#11680 EPEL9 not listed in MDAPI branches
Closed: Fixed 2 years ago by humaton. Opened 2 years ago by aviso.

https://mdapi.fedoraproject.org/branches lists the following. epel9 seems to be missing.

["dist-6E", "dist-6E-epel", "epel7", "epel8", "f28", "f29", "f30", "f31", "f32", "f33", "f34", "f35", "f36", "f37", "f38", "f39", "fc36", "koji", "rawhide", "src_dist-6E", "src_dist-6E-epel", "src_epel7", "src_epel8", "src_f29", "src_f30", "src_f31", "src_f32", "src_f33", "src_f34", "src_f35", "src_f36", "src_f37", "src_f38", "src_f39", "src_fc36", "src_rawhide"]

This is related to https://github.com/badges/shields/issues/9589


Metadata Update from @phsmoura:
- Issue tagged with: medium-gain, medium-trouble, ops

2 years ago

Just wanted to add that epel9 doesn't work when retrieving information about a package, either:

Metadata Update from @humaton:
- Issue assigned to humaton

2 years ago

Hi, I have opened PR with mdapi and it was merged. Waiting for upstream release, once done and deployed in infra I will update this ticket.

a new version of MDAPI is deployed in prod, please check it and reopen this ticket if there are any issues with the epel9 branches.

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

2 years ago

Seems to be working. Do we need to do anything to make sure this doesn't happen with future EPEL versions?

@aviso There was an issue filed in the EPEL issue tracker, so we're looking at it now to make sure EPEL 10 works correctly.

@carlwgeorge That's great! Thanks for the heads up!

Log in to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog