Please branch and build python-responses in epel9. If you do not wish to maintain python-responses 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.
Let's see if we can get RedHat to ship it - see bug #2040998
(In reply to Orion Poplawski from comment #1) > Let's see if we can get RedHat to ship it - see bug #2040998 per Miro, it's actually retired. It bit me a few times already, the package is in gitlab but once you browse, there's a dead.package. Athos or @
Athos or @fschwarz - could you help branch and build this? (accidentally submitted before finishing my comment, sorry) The EPEL Packaging SIG would be happy to be a co-maintainer if you do not wish to build it on epel9 (please add the epel-packagers-sig group as collaborator on epel* branches) Additionally, I would be happy to be a co-maintainer if you do not wish to build it for epel9 (FAS salimma).
*** Bug 2045987 has been marked as a duplicate of this bug. ***
Michel: sorry, did not see your comment earlier and I did not realize I became an admin some time ago so I thought this was just part of the python-sig stack. I'll go through the issues this evening and get everything updated/branched. However I always like additional co-maintainers. EPEL sig+salimma FTW. What is the EPEL sig user name to use in pagure?
quick question: How can I run a mockbuild for EPEL 9 manually? $ mock --rebuild -r /etc/mock/epel-next-9-x86_64.cfg python-responses-0.17.0-1.fc36.src.rpm ... No match for argument: fedpkg-minimal Error: Unable to find a match: fedpkg-minimal Any way to trigger a local build?
By `mock -r centos-stream+epel-9-x86_64 ...`.
@Pavel: Thanks, that worked for me (after installing the mock packages from updates-testing) epel9 branch requested: https://pagure.io/releng/fedora-scm-requests/issue/41352 @Michel: I made you a co-admin for python-responses. I can do the initial EPEL 9 build but I'm absolutely happy if someone else also has an eye on python-responses. Feel free to add also the EPEL-sig.
FEDORA-EPEL-2022-051178a1ea has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-051178a1ea
FEDORA-EPEL-2022-051178a1ea 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-051178a1ea See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-051178a1ea has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.