EPEL 10 hasn't launched yet, but we're already working on getting parts of it working. Builds work, and the intention is to have those builds go straight to a "stable" repo similar to Rawhide, until we officially launch EPEL 10 and enable the testing repo. Our first attempt at this involved automatic bodhi updates (again, similar to Rawhide) but using bodhi to create the composes. That hasn't worked out well (see the issue below) so we want to switch it to being composed on a nightly cron job (again, similar to Rawhide). https://pagure.io/releng/issue/12256 I have two pull requests open that implement this, and I've already manually tested the nightly script with an alternate sync destination and it works as expected. https://pagure.io/pungi-fedora/pull-request/1341 https://pagure.io/fedora-infra/ansible/pull-request/2230 This would also involve changing settings on the EPEL-10.0 bodhi release (state and composed-by-bodhi). I feel like these changes are safe for a freeze break and shouldn't impact Fedora in any way. In the unlikely event this doesn't work as planned, rolling back would just involve reverting the second pull request. Can I get some +1's for this plan? -- Carl George -- _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
