#124 Add epel8-next, epel9, and epel9-next
Opened 8 months ago by salimma. Modified 4 months ago

CentOS Stream 9 has been launched, and CentOS 8 is EOL-ed... tomorrow. There's likely to be increasing activities in these branches:

  • epel8-next, for packages that need to be rebuilt for Stream 8 because of ABI change from the latest EL (e.g. recently, the Qt update)
  • epel9, as we are bootstrapping EPEL for (RH)EL9 using CentOS Stream 9 as base
  • epel9-next, once RHEL9 goes GA and Stream 9 becomes the pre-release for 9.1

Currently only epel8 is available, so we should add these three.


So this is because https://admin.fedoraproject.org/pkgdb/api/collections/ does not have these branches listed. Given pkgdb is deprecated -- should mdapi get the list of active releases from another source? What should that be?

So this is because https://admin.fedoraproject.org/pkgdb/api/collections/ does not have these branches listed. Given pkgdb is deprecated -- should mdapi get the list of active releases from another source? What should that be?

That file is manually maintained by the infra team via ansible. You can open a
PR to the ansible repo to update it, it will then be pushed to the proxies and
picked up by mdapi :)

ok, so we updated and it handled epel9 fine.

But... it does not handle the '-next' versions:

Traceback (most recent call last):
 File "/code/mdapi-get_repo_md", line 555, in <module>
     main()
   File "/code/mdapi-get_repo_md", line 511, in main
     for idx, url in enumerate(urls[release['name']]):
 KeyError: 'Fedora EPEL Next'

So, we need to fix that and then we can re-add it back in...

Login to comment on this ticket.

Metadata