If you do not wish to maintain libEMF in epel8/epel9/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/libEMF/addgroup and grant it commit access, or collaborator access on epel* branches. Rebuilding libEMF-1.0.13-14.fc42 against epel8/epel9/epel10 target seems to work without any changes required.
Sorry, I only checked EL10 and didn't check the availability in EL9 and EL8 - where it exists. Thus this request is only for EPEL 10.
(In reply to Robert Scheck from comment #1) > Sorry, I only checked EL10 and didn't check the availability in EL9 and EL8 > - where it exists. Thus this request is only for EPEL 10. It exists in RHEL8 and RHEL9, actually, not EPEL. It looks like it wasn't included in RHEL10. What do you need it for?
FEDORA-EPEL-2025-b6828f87f2 (libEMF-1.0.13-15.el10_0) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-b6828f87f2
(In reply to Dominik 'Rathann' Mierzejewski from comment #2) > What do you need it for? Dia has (after the update I am currently working on) a plugin that uses libEMF. But Dia will be in EPEL 10 and thus libEMF in EPEL 10 will be fine, too.
FEDORA-EPEL-2025-b6828f87f2 has been pushed to the Fedora EPEL 10.0 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-b6828f87f2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-b6828f87f2 (libEMF-1.0.13-15.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository. If problem still persists, please make note of it in this bug report.