Please branch and build gprolog in epel8 and epel9. If you do not wish to maintain gprolog 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/gprolog/addgroup and grant it commit access, or collaborator access on epel* branches.
This seems to build out of the box for both branches fwiw.
Will you be able to branch and build gprolog 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 epel9.
https://pagure.io/releng/fedora-scm-requests/issue/47338 https://pagure.io/releng/fedora-scm-requests/issue/47339
FEDORA-EPEL-2022-ddd64acded has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-ddd64acded
FEDORA-EPEL-2022-80f969d4a4 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-80f969d4a4
FEDORA-EPEL-2022-ddd64acded 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-ddd64acded See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-80f969d4a4 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-80f969d4a4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-ddd64acded has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-80f969d4a4 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.