Please branch and build SDL_image in epel8 and epel9. If you do not wish to maintain SDL_image 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/SDL_image/addgroup and grant it commit access, or collaborator access on epel* branches.
I'm sorry but I don't have time to maintain EPEL branches of the packages which I (co)maintain. As requested I've given commit rights to the epel-packagers-sig group so that the EPEL Packagers SIG can create and maintain the requested branches.
Thanks! Branches requested: $ fedpkg request-branch epel8 https://pagure.io/releng/fedora-scm-requests/issue/46869 $ fedpkg request-branch epel9 https://pagure.io/releng/fedora-scm-requests/issue/46870
FEDORA-EPEL-2022-c968e710f0 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-c968e710f0
FEDORA-EPEL-2022-12d9e3a933 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-12d9e3a933
FEDORA-EPEL-2022-12d9e3a933 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-12d9e3a933 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-c968e710f0 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-c968e710f0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-c968e710f0 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-12d9e3a933 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.