#12671 Errors during downloading metadata for repository 'epel':
Closed: Fixed by carlwgeorge. Opened by leiyang.

  • Describe the issue
    Errors during downloading metadata for repository 'epel':
  • Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=epel-10.0&arch=x86_64 (IP: 54.180.100.16)
  • Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=epel-10.0&arch=x86_64 (IP: 13.233.179.58)
  • Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=epel-10.0&arch=x86_64 (IP: 38.145.60.20)
    Error: Failed to download metadata for repo 'epel': Cannot prepare internal mirrorlist: Status code: 404 for https://mirrors.fedoraproject.org/metalink?repo=epel-10.0&arch=x86_64 (IP: 38.145.60.20)

  • When do you need this? (YYYY/MM/DD)
    Always

  • If we cannot complete your request, what is the impact?
    This will affect daily testing and some packages will fail to install.


CC: @carlwgeorge

Metadata Update from @carlwgeorge:
- Issue assigned to carlwgeorge

This is related to the work that took place in epel#324. Originally our plan for EPEL 10 was to have the following repo names in mirrormanager:

  • epel-10 for CentOS
  • epel-10.0, epel-10.1, etc. for RHEL

Because of the upgrade issue described in that issue, we pivoted to these repo names:

  • epel-10 for CentOS
  • epel-z-10 for RHEL

epel-release-10-5.el10_0 uses these repo names, so once you update to that you should have working repos. If you previously edited the repo files you may need to also merge in the relevant .rpmnew files. Since RHEL 10 hasn't launched yet, we didn't set up redirects for the old epel-10.0. I'm not necessarily against it, but you'll need to upgrade epel-release eventually, because even if we put epel-10.0 redirects in place we won't keep doing it for future minor versions.

I went ahead and added the following repo redirects:

  • epel-10.0epel-z-10.0
  • epel-debug-10.0epel-z-debug-10.0
  • epel-source-10.0epel-z-source-10.0
  • testing-epel10.0epel-z-testing-10.0
  • testing-debug-epel10.0epel-z-testing-debug-10.0
  • testing-source-epel10.0epel-z-testing-source-10.0

That should assist any RHEL systems that still have the old epel-release installed to upgrade to the new one.

Metadata Update from @carlwgeorge:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata Update from @carlwgeorge:
- Issue tagged with: low-gain, low-trouble

Metadata