Description of problem: It seems that when epel branched 10.0, it should have created 10.1 that would point to 10. Otherwise, on rhel-10.1 epel repos can't be found: Errors during downloading metadata for repository 'epel': - Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=epel-10.1&arch=x86_64 (IP: 18.192.40.85) - Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=epel-10.1&arch=x86_64 (IP: 152.19.134.198) - Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=epel-10.1&arch=x86_64 (IP: 38.145.60.21) Error: Failed to download metadata for repo 'epel': Cannot prepare internal mirrorlist: Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=epel-10.1&arch=x86_64 (IP: 152.19.134.198)
All those minor 10.x 10.y are going to hurt
The EPEL Steering Committee is working on some changes to the EPEL 10 repo structure to address upgrade path concerns. https://pagure.io/epel/issue/324 Once that work is complete, pre-release RHEL 10.1 systems will be able to request EPEL 10.1 by setting their releasever DNF variable to 10.1.
FEDORA-EPEL-2025-c37fe4fbd9 (epel-release-10-5.el10_0) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-c37fe4fbd9
FEDORA-EPEL-2025-c37fe4fbd9 has been pushed to the Fedora EPEL 10.0 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-c37fe4fbd9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-c37fe4fbd9 (epel-release-10-5.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository. If problem still persists, please make note of it in this bug report.
This update is live for EPEL 10.0 and 10.1. The default metalinks work as follows. CentOS 10 systems don't have releasever_minor defined, and thus will request an epel-10 repo from mirrormanager, which returns EPEL 10.1 repos. root@c10:~# dnf -q --repo epel repolist -v | grep -e Repo-metalink -e Repo-baseurl Repo-metalink : https://mirrors.fedoraproject.org/metalink?repo=epel-10&arch=x86_64 Repo-baseurl : http://mirror.nodesdirect.com/epel/10.1/Everything/x86_64/ (221 more) RHEL 10 systems have releasever_minor defined, and thus will request an epel-z-10 repo from mirrormanager, which returns EPEL 10.0 repos. root:~# dnf -q --repo epel repolist -v | grep -e Repo-metalink -e Repo-baseurl Repo-metalink : https://mirrors.fedoraproject.org/metalink?repo=epel-z-10&arch=x86_64 Repo-baseurl : https://nocix.mm.fcix.net/epel/10.0/Everything/x86_64/ (226 more) If you're using a pre-release RHEL 10.1 system, you'll need to override releasever to 10.1. root:~# dnf -q --releasever 10.1 --repo epel repolist -v | grep -e Repo-metalink -e Repo-baseurl Repo-metalink : https://mirrors.fedoraproject.org/metalink?repo=epel-z-10.1&arch=x86_64 Repo-baseurl : https://mirror.fmt-2.serverforge.org/epel/10.1/Everything/x86_64/ (226 more)
If you can't use metalinks for whatever reason and need to configure a baseurl, use the commented out example in epel.repo as a template. Properly configured, it should work as follows. CentOS 10 systems don't have releasever_minor defined, and thus will request a repo under the path epel/10 (a symlink to epel/10.1). root@c10:~# dnf -q --repo epel repolist -v | grep Repo-baseurl Repo-baseurl : https://mirror.fcix.net/epel/10/Everything/x86_64/ RHEL 10 systems have releasever_minor defined, and thus will request a repo under the path epel/10z (a symlink to epel/10.0). root:~# dnf -q --repo epel repolist -v | grep Repo-baseurl Repo-baseurl : https://mirror.fcix.net/epel/10z/Everything/x86_64/ If you're using a pre-release RHEL 10.1 system, you'll need to override releasever to 10.1, which will request a repo under the path epel/10.1z (a symlink to epel/10.1). root:~# dnf -q --releasever 10.1 --repo epel repolist -v | grep Repo-baseurl Repo-baseurl : https://mirror.fcix.net/epel/10.1z/Everything/x86_64/