On Wed, Feb 19, 2025 at 5:50 AM Carl George via epel-announce <epel-announce@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > 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. As a temporary workaround until this is fixed in fedpkg, you can add the `--no-auto-module` flag when running `fedpkg request-branch epel10.0`, which prevents creation of the two unwanted / wrong tickets. Fabio -- _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
