Please branch and build mingw-libxml2 in epel9. If you do not wish to maintain mingw-libxml2 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/mingw-libxml2/addgroup and grant it commit access, or collaborator access on epel* branches. I would also be happy to be a co-maintainer (FAS: orion). We will require an ExclusiveArch until RHEL 9.1 when they should be shipping the mingw-gcc packages on all arches. Scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=90769511
Will you be able to branch and build mingw-libxml2 in epel9? The EPEL Packagers SIG would be happy to be a co-maintainer if you do not wish to build it on epel9.
Yes, I guess so. I have added epel-packagers-sig as committer. Do I need to request the branch?
Branch requested: https://pagure.io/releng/fedora-scm-requests/issue/50270
FEDORA-EPEL-2023-f1866e3ba2 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-f1866e3ba2
FEDORA-EPEL-2023-f1866e3ba2 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-f1866e3ba2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2023-f1866e3ba2 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.