We currently have a symlink pointing to the latest release of the epel-release package to provide a permanent non-changing URL for users to install it.
https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ➡ https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64/Packages/e/epel-release-8-13.el8.noarch.rpm
It would be beneficial for users to also have a similar symlink for epel-next-release.
https://dl.fedoraproject.org/pub/epel/epel-next-release-latest-8.noarch.rpm ➡ https://dl.fedoraproject.org/pub/epel/8/Everything/x86_64/Packages/e/epel-next-release-8-13.el8.noarch.rpm
Non-emergency ASAP. There is no deadline strictly speaking, but this would be immediately useful. I have an EPEL documentation pull request open that references the symlink, which I don't want to merge until the symlink is in place.
n/a
CentOS Stream users who want to install the latest epel-next-release via URL have to check in the directory structure to find the exact current release URL. If they put that URL into their automation, they risk it breaking in the future the next time the release is incremented.
I'd like to work on it, if that's ok
Metadata Update from @mohanboddu: - Issue assigned to phsmoura - Issue tagged with: medium-gain, medium-trouble, ops
Just did the PR suggesting the changes. https://pagure.io/fedora-infra/ansible/pull-request/869
I see that https://pagure.io/fedora-infra/ansible/pull-request/869 has been merged. It seems to be working correctly for epel8-next.
$ rpm -qp https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm epel-release-8-13.el8.noarch $ rpm -qp https://dl.fedoraproject.org/pub/epel/epel-next-release-latest-8.noarch.rpm epel-next-release-8-13.el8.noarch
However, something appears to be wrong with the epel9-next symlink. It's using the same source (the main epel-release package) for both links.
$ rpm -qp https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm epel-release-9-1.el9.next.noarch $ rpm -qp https://dl.fedoraproject.org/pub/epel/epel-next-release-latest-9.noarch.rpm epel-release-9-1.el9.next.noarch
I think I see the issue. Our first build of epel-release was published in EPEL 9 Next, and includes next in the disttag of both epel-release and epel-next-release. The glob is matching that I think. We should be able to work around it for now by pulling https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2021-341875060f from stable and re-pushing.
next
Hey @carlwgeorge! I forgot to update here, sorry.
So, that PR throw an no path specified error and I did another PR fixing it. It was merged too, although it was merged 5 days ago... that is my latest PR:
no path specified
https://pagure.io/fedora-infra/ansible/pull-request/889
I tried out those commands to see if the symlink is point to the same file, but got different result
$ rpm -qp https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm epel-release-9-2.el9.noarch $ rpm -qp https://dl.fedoraproject.org/pub/epel/epel-next-release-latest-9.noarch.rpm epel-release-9-1.el9.next.noarch
Is it working as expected?
The expected result is the following symlinks:
https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm -> https://dl.fedoraproject.org/pub/epel/9/Everything/x86_64/Packages/e/epel-release-9-2.el9.noarch.rpm
https://dl.fedoraproject.org/pub/epel/epel-next-release-latest-9.noarch.rpm -> https://dl.fedoraproject.org/pub/epel/9/Everything/x86_64/Packages/e/epel-next-release-9-2.el9.noarch.rpm
This has been working since https://pagure.io/fedora-infra/ansible/pull-request/889 was merged. Thanks y'all!
Metadata Update from @carlwgeorge: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.