EPEL 10 now uses zstd compression, which means that createrepo_c on CBS infrastructure needs to be upgraded to at least createrepo_c-0.20.1-4.el9 so mergerepos_c can handle EPEL 10 repodata.
createrepo_c
createrepo_c-0.20.1-4.el9
mergerepos_c
Otherwise newRepo tasks will continue to fail like this one: https://cbs.centos.org/koji/taskinfo?taskID=4955103
newRepo
nice .. the latest available version on RHEL9.6 is : 0.20.1-2.el9
0.20.1-2.el9
So that means that epel10 can't be parsed on rhel9 ? I can rebuild the version from Stream (not yet in RHEL) : https://kojihub.stream.centos.org/koji/buildinfo?buildID=75952 and so overwrite a distro package.
@carlwgeorge : can you comment on that ? why is RHEL 9.6 not even able to parse repodata from epel10 ? was the expected behaviour and if so, can that be announced somewhere ?
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue tagged with: cbs, high-gain, investigation, medium-trouble
Yes. This is pending for 9.7. There's a Jira about it: https://issues.redhat.com/browse/RHEL-67689
Rebuilt it in infra9 buildtools tags : https://cbs.centos.org/koji/buildinfo?buildID=60617 Tagged to -release Then waited for distrepo task to have finished (and pkgs being gpg signed ) Once available on internal mirror used for isolated builders, ansible applied the change on all koji builders:
Kojira was restarted and tried to regen repo for bunch of (previously failing) tags (using epel), including this one, now working : https://cbs.centos.org/koji/taskinfo?taskID=4957305
Closing but let's try to communicate such change in advance, especially for people knowing that such change is coming please ;)
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
We had originally planned to have EPEL 10 start with zstd repodata, but the implementation didn't get submitted until just two weeks before we did the official launch. There was some iteration and discussion, and eventually we added it to the agenda for the EPEL Steering Committee meeting. We agreed to move forward with the change, and it was merged and deployed about two weeks ago. At the time we thought the only impact would be people running mirrors on RHEL and performing mergerepo_c to retain previous packages. We did not anticipate that it would also affect koji instances using EPEL as an external repo. We apologize for this oversight, for the trouble this caused you, and for not announcing the change in advance.
Log in to comment on this ticket.