Please branch and build msitools in epel8 and epel9. If you do not wish to maintain msitools 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/msitools/addgroup and grant it commit access, or collaborator access on epel* branches.
I added the epel-packagers-sig group. You may have to update the wxi files, or disable the check.
Could you double check that you've set "epel*" as the allowed branches for epel-packagers-sig? It doesn't look like I'm able to request branches. Thanks!
(In reply to Davide Cavalca from comment #2) > Could you double check that you've set "epel*" as the allowed branches for > epel-packagers-sig? It doesn't look like I'm able to request branches. > Thanks! I don't see how to do that. I have simply added user/group: epel-packagers-sig (collaborator)
On https://src.fedoraproject.org/rpms/msitools/addgroup add epel-packagers-sig, select collaborator, and write epel* in the text box that appears right after (the one labeled with "a comma separated list of branches").
(In reply to Davide Cavalca from comment #4) > On https://src.fedoraproject.org/rpms/msitools/addgroup add > epel-packagers-sig, select collaborator, and write epel* in the text box > that appears right after (the one labeled with "a comma separated list of > branches"). done
FEDORA-EPEL-2023-88b53c1bfb has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-88b53c1bfb
FEDORA-EPEL-2023-1872966bee has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-1872966bee
FEDORA-EPEL-2023-1872966bee 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-2023-88b53c1bfb has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.