Thanks for the heads-up on EPEL 10. ₣rom the view of a Fedora packager who maintains EPEL branches as a way of "paying back" (for infra etc), there is the following problem: There seem to be mass requests for branching packages for EPEL 10 which sound as if we just had to branch and build, maybe adjust. As a matter of fact, the hardest part is getting all prerequisites into EPEL first. From such mass requests I expect that at least build requires and requires have been checked and blockers set up in bugzilla accordingly, or at least *mentioned*. The way it's being done now I've churned time on this to new avail. The easy way out is letting the sig to handle this. (And the sig's FAS handle is wrong in the ticket, too.) So, please, let's make each others' work as easy as possible. Michael -- _______________________________________________ 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
