github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-13 02:57:44 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

gitea-1.8.0-rc3-linux-amd64.sha256 exposes wrong file? #3186

New Issue
Closed
opened 2025-11-02 05:03:11 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 05:03:11 -06:00
Owner
Copy Link

Originally created by @Perflyst on GitHub (Apr 14, 2019).

In the releases is a file gitea-1.8.0-rc3-linux-amd64.sha256 which has gitea-master-linux-amd64 listed instead of gitea-1.8.0-rc3-linux-amd64

d24df15bda3a301fd71ee814d0672f1d9ce7efe88b39fa5f9aebe59506bb9f24 gitea-master-linux-amd64

Originally created by @Perflyst on GitHub (Apr 14, 2019). In the releases is a file `gitea-1.8.0-rc3-linux-amd64.sha256` which has `gitea-master-linux-amd64` listed instead of `gitea-1.8.0-rc3-linux-amd64` `d24df15bda3a301fd71ee814d0672f1d9ce7efe88b39fa5f9aebe59506bb9f24 gitea-master-linux-amd64`
GiteaMirror added the type/bugtopic/build labels 2025-11-02 05:03:11 -06:00
GiteaMirror commented 2025-11-02 05:03:12 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 14, 2019):

Where did you mean? github releases or dl.gitea.io?

@lunny commented on GitHub (Apr 14, 2019): Where did you mean? github releases or dl.gitea.io?
GiteaMirror commented 2025-11-02 05:03:12 -06:00
Author
Owner
Copy Link

@Perflyst commented on GitHub (Apr 14, 2019):

GitHub releases

@Perflyst commented on GitHub (Apr 14, 2019): GitHub releases
GiteaMirror commented 2025-11-02 05:03:12 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 14, 2019):

@techknowlogick is 1.8rc3's binaries released via drone-cli ?

@lunny commented on GitHub (Apr 14, 2019): @techknowlogick is 1.8rc3's binaries released via drone-cli ?
GiteaMirror commented 2025-11-02 05:03:13 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Apr 14, 2019):

I had to rename the files due to combination of make and drone exec --event tag --ref v1.8.0-rc3 --repo go-gitea/gitea setting the file name to be master instead of correct tag. I chose to rename instead of keep master in name so that some auto update scripts that target binaries directly still function. The recently merged PR will resolve this for future builds (and the backport that isn't yet merged will solve this for stable 1.8.0 build). The is same for 1.7.6 release as well.

The above sha hashes should have incorrect filename for both github releases and dl.gitea.io. You can check that the hashes are indeed the same it just has a different filename.

@techknowlogick commented on GitHub (Apr 14, 2019): I had to rename the files due to combination of make and `drone exec --event tag --ref v1.8.0-rc3 --repo go-gitea/gitea` setting the file name to be master instead of correct tag. I chose to rename instead of keep master in name so that some auto update scripts that target binaries directly still function. The recently merged PR will resolve this for future builds (and the backport that isn't yet merged will solve this for stable 1.8.0 build). The is same for 1.7.6 release as well. The above sha hashes should have incorrect filename for both github releases and dl.gitea.io. You can check that the hashes are indeed the same it just has a different filename.
GiteaMirror commented 2025-11-02 05:03:13 -06:00
Author
Owner
Copy Link

@Perflyst commented on GitHub (Apr 14, 2019):

Yes, hashes are correct. Was just a bit confusing.

@Perflyst commented on GitHub (Apr 14, 2019): Yes, hashes are correct. Was just a bit confusing.
GiteaMirror commented 2025-11-02 05:03:13 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 15, 2019):

Let's close this when next build sha is correct.

@lunny commented on GitHub (Apr 15, 2019): Let's close this when next build sha is correct.
GiteaMirror commented 2025-11-02 05:03:13 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Apr 15, 2019):

Closing as builds now correctly build and put in correct filename. Next RC will have correct filename.

Thanks for keeping an eye on things like this.

@techknowlogick commented on GitHub (Apr 15, 2019): Closing as builds now correctly build and put in correct filename. Next RC will have correct filename. Thanks for keeping an eye on things like this.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/build type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3186
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?