I would do this myself, but I only have commit privileges on the package. I need admin or collaborator/epel to be able request the epel9 branch. Thanks.
AFAIK I don't have EPEL capabilities either.
You are the main admin of the package - you have full capabilities for Fedora and EPEL. Or you could promote my access.
If you do not wish to maintain perl-XML-RSS in 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/perl-XML-RSS/addgroup and grant it commit access, or collaborator access on epel* branches. I would also be happy to be a co-maintainer (FAS: orion). I can be the primary contact for EPEL (FAS: orion).
I assume we're still talking about perl-Data-Report even though you mention perl-XML-RSS in the previous message. I've added epel-packagers-sig to perl-Data-Report, but I see that you (orion) already have commit access.
Yes, too much sloppy cut&paste. As I said before - commit access is not enough to request a new branch. Thanks for adding epel-packagers-sig.
FEDORA-EPEL-2023-afb15a9d07 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-afb15a9d07
FEDORA-EPEL-2023-afb15a9d07 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-2023-afb15a9d07 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2023-afb15a9d07 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.