-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.9.37 has been retagged #426
Comments
said it before and now sayng it again:)
sorry for all inconvenience. |
Sure, but does that matter, if the sources are the same? I'm interested in the git tags and auto-generated tarballs, not in any platform-specific releases (since this repository does not use any git submodules).
That doesn't doesn't break downstreams any less (e.g. also anyone that has the repository checked out). Why not create pre-release tags, if something is not yet clear or needs figuring out?
For tracking purposes I would need to rely on regex matching in an HTML page to find new releases. Additionally, sourceforge has proven flaky and slow in the past. Git is far more reliable for this. |
Hi! 👋
This release has been retagged (similar to 0.9.34 in #401).
via https://gitlab.archlinux.org/archlinux/packaging/packages/qtractor/-/issues/2
The relevant diff between a source tarball downloaded on 2023-12-05 and now is:
Full diffoscope output: qtractor-0.9.37-diffoscope.log
@rncbc please just create a new tag. Retagging breaks downstream packaging and reproducibility. There really is no need for a ticket like this.
The text was updated successfully, but these errors were encountered: