It's actually missing for epel10, while pkgs are built (example : https://koji.fedoraproject.org/koji/buildinfo?buildID=2677945) Can that be pushed out and then (but probably for epel-release maintainer) .repo file added to then be able to consume/install these packages ? :D
CC: @patrikp
Metadata Update from @phsmoura: - Issue tagged with: low-gain, low-trouble, ops
Metadata Update from @patrikp: - Issue assigned to patrikp
So the way this usually works is that we generate the signed RPMs, send them to Cisco, they update their CDN and then we upload the metadata on our side.
Currently we are stuck at the step of getting the RPMs to Cisco. We used to do this via tarball attachments on e-mails but that no longer works. We are trying to contact Cisco and see how we could resolve it.
We have another ticket open with more information (and it includes EPEL10 too).
https://pagure.io/releng/issue/12617
Metadata Update from @patrikp: - Issue close_status updated to: Duplicate - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.