Per the EPEL stalled package policy - https://docs.fedoraproject.org/en-US/epel/epel-policy/#stalled_epel_requests - I have contacted the maintainer, twice, and waited the appropriate amount of time.
https://bugzilla.redhat.com/show_bug.cgi?id=2089764 - (ASK2-Jun15) https://bugzilla.redhat.com/show_bug.cgi?id=2094553 - (ASK2-Jun15) https://bugzilla.redhat.com/show_bug.cgi?id=2090432 - (ASK2-Jun15) https://bugzilla.redhat.com/show_bug.cgi?id=2094555 - (ASK2-Jun15) https://bugzilla.redhat.com/show_bug.cgi?id=2094556 - (ASK2-Jun15) https://bugzilla.redhat.com/show_bug.cgi?id=2094557 - (ASK2-Jun15) https://bugzilla.redhat.com/show_bug.cgi?id=2087931 - (ASK2-Jun15) https://bugzilla.redhat.com/show_bug.cgi?id=2094551 - (ASK2-Jun15) https://bugzilla.redhat.com/show_bug.cgi?id=2094552 - (ASK2-Jun15)
I am a member of the epel-packagers-sig and I am requesting epel-packagers-sig be given commit permissions so that I, or a member of the SIG, might branch and build this package in epel9.
Please also add my account: tdawson
When do you need this? (YYYY/MM/DD) 2022/07/01
When is this no longer needed or useful? (YYYY/MM/DD) N/A
If we cannot complete your request, what is the impact? The are dependencies for fedpkg. We will not be able to build fedpkg in epel9
Metadata Update from @phsmoura: - Issue tagged with: low-gain, low-trouble, ops
Please, when you do this, make sure to set the Buzgilla contact for EPEL to epel-packagers-sig or tdawson. I've noticed that e.g. python-lockfile has orphan as the Buzgilla contact for EPEL.
I've also opened https://pagure.io/releng/issue/10866
You and epel-packagers-sig are now a collaborator on the epel branches for the package.
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)