Describe the issue
At the 2021-11-24 EPEL Steering Committee meeting, we decided to implement plan C for the epel9 rollout. This means we will announce epel9 and epel9-next at the same time, using the c9s buildroot as an external repo for both. epel9-next is already all set up and ready to go. All we have to do is finish setting up epel9. Most of the tag structure is already set up. I believe the only remaining koji changes are:
When do you need this? (YYYY/MM/DD)
2021-12-03
When is this no longer needed or useful? (YYYY/MM/DD)
2032 (RHEL9 EOL)
If we cannot complete your request, what is the impact?
Prevents launching epel9 at the same time as epel9-next.
Metadata Update from @humaton: - Issue tagged with: medium-gain, medium-trouble, ops
$ koji edit-external-repo rhel9-base --url 'https://infrastructure.fedoraproject.org/repo/centos/centos-9-stream/$arch/' -m bare -t epel9-base $ koji add-target epel9 epel9-build epel9-testing-candidate $ koji add-target epel9-candidate epel9-build epel9-testing-candidate
I could add c9s-buildroot as external buildroot for epel9-base as its being used by epel9-next-base, so I left it rhel9-base, if needed I can change it to something else.
c9s-buildroot
rhel9-base
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
One last thing related thing I forgot to mention, can you also tag fedpkg-minimal-1.2.0-4.el9.next to epel9-override?
Mohan took care of the tag in IRC, and I was able to complete a scratch build. Thanks!