Learn more about these different git repos.
Other Git URLs
When a new tag is created the release isn't automatically added to https://releases.pagure.org/certmonger/ . Is that expected to be done manually?
Also, on https://pagure.io/certmonger/releases the releases ARE created automatically but concatenate the tag name into the tarball and directory names. certmonger has always used the format certmonger-x.x.x as tags. I gather I need to change the tagging of my project(s) to match this requirement or is it configurable somewhere?
@rcritten I think there's some confusion here. releases.pagure.org is for manually-created tarballs. If you're expecting auto-generated tarballs, those are made upon request from the generator URL: https://pagure.io/<repo>/archive/<tag>/<repo>-<version>.tar.gz.
releases.pagure.org
https://pagure.io/<repo>/archive/<tag>/<repo>-<version>.tar.gz
The name of the directory will be named after the base name of the tarball requested. So no changes to your tagging structure is required.
Ok, I had some past (false) memory of releases.pagure.org getting created automatically, I'll manually add those.
As for the tagging, it is definitely naming things wrong:
For example, the latest release tarball on https://pagure.io/certmonger/releases for tag certmonger-0.79.9 is: https://pagure.io/certmonger/archive/certmonger-0.79.9/certmonger-certmonger-0.79.9.tar.gz
The contents are:
drwxr-xr-x git/git 0 2020-02-02 10:46 certmonger-certmonger-0.79.9/ -rw-r--r-- git/git 71 2020-02-02 10:46 certmonger-certmonger-0.79.9/LICENSE -rw-r--r-- git/git 2009 2020-02-02 10:46 certmonger-certmonger-0.79.9/Makefile.am -rw-r--r-- git/git 1722 2020-02-02 10:46 certmonger-certmonger-0.79.9/README.md ...
Try: https://pagure.io/certmonger/archive/certmonger-0.79.9/certmonger-0.79.9.tar.gz
https://pagure.io/certmonger/archive/certmonger-0.79.9/certmonger-0.79.9.tar.gz
Yes, that works. The link in the little disk icon doesn't point here though.
It won't, as that one is formulaically structured, and assumes a specific tag convention. But the way the underlying generator works, you can get correctly structured tarballs. This little feature is mostly designed to deal with Java and GNOME packages that use sometimes-insane tagging conventions (mostly CVS/SVN style tags for monorepos).
If you want the links to work, you'll need to change your tagging convention. If that's okay with you, then go for that.
Ok, thanks for the confirmation and the alternate link.
Login to comment on this ticket.