Please branch and build pl in epel8 and epel9. If you do not wish to maintain pl in epel8 and epel9, or do not think you will be able to do this in a timely manner, the EPEL Packagers SIG would be happy to be a co-maintainer of the package; please add the epel-packagers-sig group through https://src.fedoraproject.org/rpms/pl/addgroup and grant it commit access, or collaborator access on epel* branches.
Put up https://src.fedoraproject.org/rpms/pl/pull-request/1 with the changes required for this to build properly in EPEL.
I have made the epel-packagers-sig group a collaborator for epel* branches. I prefer that somebody in the SIG take care of building for EPEL.
Thanks! Branches requested: $ fedpkg request-branch epel8 https://pagure.io/releng/fedora-scm-requests/issue/46823 $ fedpkg request-branch epel9 https://pagure.io/releng/fedora-scm-requests/issue/46824
FEDORA-EPEL-2022-42763cc9f6 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-42763cc9f6
FEDORA-EPEL-2022-3932e1e94c has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-3932e1e94c
FEDORA-EPEL-2022-3932e1e94c has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-3932e1e94c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-42763cc9f6 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-42763cc9f6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-3932e1e94c has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-42763cc9f6 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.