The epel-release-latest links used in the EPEL getting started guide are symlinks on the mirror created by the new-updates-sync script. We currently have two different epel-release packages in different EPEL 10 minor versions:
* EPEL 10.2: epel-release-10-8.el10_2 * EPEL 10.3/10.4: epel-release-10-9.el10_3
The is part of a bigger migration [0], but the short version is that the newer build only works on CentOS, the older build works on both CentOS and RHEL, and the latest symlink needs to stay on the older build. It was initially, but earlier this week it switched to the newer build. This caused at least one RHEL user to install the wrong package and get dependency errors [1]. As a short term fix, I manually switched the epel-release-latest-10.noarch.rpm symlink back to the 10.2 path, and commented out the function call in new-updates-sync script that updates the symlinks. For a long term fix, I have proposed a change to the script to allow explicitly excluding an EPEL release from the symlink generation [2]. For EPEL 10 we'll always exclude all but the oldest active minor version.
I feel like this change is relatively safe for a freeze break and shouldn't impact Fedora in any way. In the unlikely event this doesn't go as planned, we can roll it back by reverting the pull request. Kevin already gave a +1 on the PR. Anyone else?
[0] https://discussion.fedoraproject.org/t/looking-back-at-epel-10-and-forward-t... [1] https://bugzilla.redhat.com/show_bug.cgi?id=2521652 [2] https://forge.fedoraproject.org/infra/ansible/pulls/3642
infrastructure@lists.fedoraproject.org
-
Carl George