Please branch and build python-rpmautospec in epel9. If you do not wish to maintain python-rpmautospec in epel9, or do not think you will be able to do this in a timely manner, I would be happy to be a co-maintainer of the package.
Please?
I'd rather not maintain this in EPEL 9 myself, so asking again. Could you please do that?
Perhaps Nils would have time to work on this? If it's just branch and build I could do it, but it would be good to do a bit more testing...
This bug appears to have been reported against 'rawhide' during the Fedora 36 development cycle. Changing version to 36.
Nils, Adam, anybody?
It's been awhile with no update, so let's have EPEL Packagers SIG co maintain this. I'll file a stalled request releng ticket Per EPEL policy, we can always drop this later if it's too tedious to maintain
Stalled request filed: https://pagure.io/releng/issue/10672
$ fedpkg request-branch --repo python-rpmautospec epel9 https://pagure.io/releng/fedora-scm-requests/issue/42608
*** Bug 2046036 has been marked as a duplicate of this bug. ***
Just so people know this has been branched for epel9. But the build currently fails on tests/%check
Sorry for missing this for so long. I'll look into this.
FEDORA-EPEL-2022-3c4efd0b6a has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-3c4efd0b6a
This was just a matter of that building the package attempts to run the unit tests in parallel using python-pytest-xdist which so far isn't available in EL9 (see https://bugzilla.redhat.com/show_bug.cgi?id=2032588). I've patched the spec file and submitted an update.
FEDORA-EPEL-2022-3c4efd0b6a 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-3c4efd0b6a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-3c4efd0b6a has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.