Please branch and build ppl in epel8 and epel9. If you do not wish to maintain ppl 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/ppl/addgroup and grant it commit access, or collaborator access on epel* branches.
I don't think either ppl maintainer is active in Fedora anymore. I have used my provenpackager abilities in the past to maintain this package due to lack of responsiveness of the maintainers of record.
We can use the stalled EPEL package policy to unblock this ticket if needed: https://docs.fedoraproject.org/en-US/epel/epel-policy/#stalled_epel_requests That said, if you know that the maintainer is inactive, you may wanna start the non-responsive maintainer process: https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/
Will you be able to branch and build ppl in epel8 and epel9? The EPEL Packagers SIG would be happy to be a co-maintainer if you do not wish to build it on epel8 and epel9.
Sorry, I noticed now that I am the assignee of this ticket. I must say that I do not understand what is asked here, but what I can say is that you can count on cooperation upstream. Just write to ppl-devel.it a description of what is required.
Thanks Roberto, I don't thing upstream needs to do anything specific here, ppl builds out of the box on EPEL from what I can see. What we do need is for you (as maintainer of this package) to either branch and build it for EPEL 8 and EPEL 9, or to add the EPEL Packagers SIG as a co-maintainer so that we can do it on your behalf and help maintain this package in EPEL going forward. You can do that by adding the epel-packagers-sig group through https://src.fedoraproject.org/rpms/ppl/addgroup and granting it commit access, or collaborator access on epel* branches. Thanks!
Done! Please do not hesitate to get in touch if anything else is needed. Thanks for your assistance.
Thanks! Branches requested: $ fedpkg request-branch epel8 https://pagure.io/releng/fedora-scm-requests/issue/47255 $ fedpkg request-branch epel9 https://pagure.io/releng/fedora-scm-requests/issue/47256
FEDORA-EPEL-2022-4fe1569611 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-4fe1569611
FEDORA-EPEL-2022-4fe1569611 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-4fe1569611 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-6fec4c6e57 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-6fec4c6e57
FEDORA-EPEL-2022-6fec4c6e57 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-6fec4c6e57 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-4fe1569611 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-6fec4c6e57 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.