In the refs page here: https://git.sr.ht/~sircmpwn/aerc/refs
The .tar.gz for 0.5.2 (latest version) is: https://git.sr.ht/~sircmpwn/aerc/archive/fb67d1f5a3f6fe875d74581aff59c79817a7b9f4.tar.gz
While the .tar.gz naming for 0.4.0 release is: https://git.sr.ht/~sircmpwn/aerc/archive/0.4.0.tar.gz
It'd be great if instead of the commit hash, you could change the URL to vendor a specific version at tha page - like it has been done for 0.4.0. Same stuff also applies to 0.5.0 and 0.5.1 versions whose .tar.gz URL at that page are commit hashes instead.
Since this becomes harder for downstream of your package (speaking from the perspective of Debian in this case) to reliably track and automate fetching of versions and maintain them, it'd be great if you consider to fix URLs to consistent format at that page.
Actually, e.g. 0.5.0.tar.gz does exist. sr.ht appears to determine which URL to link on the refs page based on whether the tag existed when the commit was pushed. This is not an issue for upstreams - the only effect is that the hash is used for manual downloads.
- Noam Preil
Correction: this is not an issue for downstreams.
This is not a valid bug. The correctly tagged URLs - e.g. https://git.sr.ht/~sircmpwn/aerc/archive/0.5.2.tar.gz - do exist, as you can see by opening that link. As such, there are no issues for automation of version tracking.
I am aware of that, but as you might observe, that 0.5.2 URL is present at the "homepage" here https://git.sr.ht/~sircmpwn/aerc/ and not at the refs page.
For full context: The idea for us as downstream is to get the desired tarball programmatically based on a particular page which tags tarballs reliably and a regular expression accompanied with it. We use something like:
$ uscan --download-version <Version_num> to get the tarball.
This is the regex being used: https://git.sr.ht/~sircmpwn/aerc/refs /~sircmpwn/aerc/archive/(\d\S*).tar.gz
The idea is to download versions as needed - not just the latest once, we might as well need previous versions for specific purposes, and hence, this does affect us as downstream. If the tarball links could be changed to the right 0.5.2 URL, that would be very helpful for us. Otherwise, it does create a mess for us since these would be tarballs, and we cannot reliably keep track of tags.
Let me know if you need more information. Thanks for replying, and thanks for your work! :)