Bug: 0.9.2 shasum has changed #570
Labels
No Label
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind
enhancement
kind
feature
kind/proposal
kind
question
kind
refactor
kind/security
kind/testing
kind/translation
priority/critical
priority/high
priority/low
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/has-backport
status/has-pull
status/needs-backport
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/sdk
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/tea#570
Loading…
Reference in New Issue
Block a user
No description provided.
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?
describe the issue (observed vs expected behaviour)
Hello 👋 . I'm a maintainer for the Homebrew project. We noticed that the shasum for v0.9.2 of tea has changed. We wanted to verify this is legitimate before updating it in our repository. Thanks!
Relates to https://github.com/Homebrew/homebrew-core/pull/139430.
Hi @chenrui, thank you for opening this ticket (and a thanks for maintaining the homebrew project too). This is due to how git creates the archives. Could you pop over to https://github.com/go-gitea/gitea/issues/26620 and make add a comment there, as this is part of an overarching decision we'll have to make due to the nature of how git changed the output.
Or... We also publish source archives of Gitea itself to our downloads site (dl.gitea.com), would that be better for homebrew to track instead as the checksums would be more reliable as they aren't generated on demand.
@techknowlogick just left a note on the github issue.
We (homebrew) can certainly do it. I will update the artifact accordingly. Thanks for the suggestion.
actually, I could not find the source tarball in this directory, https://dl.gitea.com/tea/0.9.2/, can you just show me the source tarball there? Thanks!
Looks like source tar balls are not released together. But https://gitea.com/gitea/tea/archive/v0.9.2.tar.gz should be the related source.
it's only the main Gitea project that publishes its source to dl.gitea.com, but that's something that would probably be good for this project too.
@lunny the reported issue above is that the hash of that generated file changed due to how git changed how the archives are created.
Exactly, if we did for gitea, it might be also good to do it for the other projects as well. Thanks!