Please branch and build perl-Number-Bytes-Human in epel9. If you do not wish to maintain perl-Number-Bytes-Human 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-Number-Bytes-Human/addgroup and grant it commit access, or collaborator access on epel* branches. As of writing, perl-Number-Bytes-Human is a run-time dependency of zoneminder (RPM Fusion).
Will you be able to branch and build perl-Number-Bytes-Human in epel9? The EPEL Packagers SIG would be happy to be a co-maintainer if you do not wish to build it on epel9.
Non responsive maintainer check has been filed: https://bugzilla.redhat.com/show_bug.cgi?id=2120834
I've now filed https://pagure.io/releng/issue/10992 according to https://docs.fedoraproject.org/en-US/epel/epel-package-request/#epel_packagers_sig_members, because there was no response by the maintainer after three weeks and three attempts.
It seems strange that EPEL would have a different procedure than Fedora: https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ As the packager for ZoneMinder in RPMFusion, I am willing to maintain perl-Number-Bytes-Human since it is a dependent package. I am not in the epel-packagers-sig group, though.
Feel free to follow up the "non-responsive maintainer policy". Personally, I only care about the EPEL part of this package.
FEDORA-EPEL-2022-8f153e6706 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-8f153e6706
FEDORA-EPEL-2022-8f153e6706 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-8f153e6706 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-8f153e6706 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.