On Tue, Feb 18, 2025 at 2:16 AM Carl George via epel-announce <[email protected]> wrote: > > Hello EPEL packagers, > > Later today (2025-02-18), Release Engineering will branch epel10.0 > from epel10, in accordance with our overall branching strategy for > EPEL 10. > > https://docs.fedoraproject.org/en-US/epel/branches/#_epel_10 > > During the branching, we will temporarily disable builds to the > epel10-candidate target, which is used when you run `fedpkg build` > from the epel10 branch. If you are trying to create a build and > receive an error about a target not existing, please try again later > in the day. Because this is the first time we are doing an EPEL mass > branching, we don't know precisely how long it will take or how long > we will need to disable the builds for. > > Thanks in advance for your patience. > > -- > Carl George > > -- > _______________________________________________ > epel-announce mailing list -- [email protected] > To unsubscribe send an email to [email protected] > 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/[email protected] > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue
We have completed mass branching for epel10.0. The epel10-candidate target has been restored, and you can resume building from the epel10 branch. Doing so will result in builds for EPEL 10.1. EPEL 10.0 builds that were submitted before the branching point are being tracked and will get tagged into epel10.1 once they reach stable status and get the epel10.0 tag. If you still want to build specifically for EPEL 10.0, you can build from the epel10.0 branch. If you request an epel10 branch for a package after this point, the epel10.0 branch will not be created automatically and must be requested separately. Please note that a bug in fedpkg was discovered today and that a request for an epel10.0 branch will also result in invalid requests for a corresponding repo and branch in the modules namespace. These can be closed as invalid, while the epel10.0 branch request in the rpms namespace should process correctly. We hope to get this fixed in fedpkg soon. Thanks for your patience and happy packaging! -- Carl George -- _______________________________________________ epel-devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
