Please branch and build mxml in epel10. If you do not wish to maintain mxml in epel10, 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/mxml/addgroup and grant it commit access, or collaborator access on epel* branches.
Will you be able to branch and build mxml in epel10? The EPEL Packagers SIG would be happy to be a co-maintainer if you do not wish to build it on epel10.
I would very much like to move to mxml 4.0.x before merging into epel10. I have a spec/build for that for rawhide, but I haven't had time yet to test dependent packages. It's a pretty big upgrade (new soname, things changing from mxml to mxml4, etc). If someone would like to help out with impact that would be great. Otherwise I will try and do so as time permits.
So, two things: I am orphaning mxml. I don't have time or interest for it, so you can take it. But also... I looked and while Carla Buildrequires mxml, it doesn't seem like it uses it? Or I could be missing something...
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
FEDORA-EPEL-2025-aa341f0d2d (mxml-3.3.1-8.el10_1) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-aa341f0d2d
I've branched v3 for EPEL 10 now, thanks to Carl's help cleaning up the spec. For v4, the plan is to make a v3 compat package, update everything that currently BRs mxml-devel to use it, and then update this package to v4 in rawhide.
FEDORA-EPEL-2025-aa341f0d2d has been pushed to the Fedora EPEL 10.1 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-aa341f0d2d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-aa341f0d2d (mxml-3.3.1-8.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository. If problem still persists, please make note of it in this bug report.