Description of problem: Hello, can you, please provide, an epel8 update for this package?
Ping :).
So, looking at this, it looks like we need: DEBUG util.py:600: No matching package to install: 'python3-aiohttp' DEBUG util.py:600: No matching package to install: 'python3-boto' DEBUG util.py:600: No matching package to install: 'python3-contextlib2' DEBUG util.py:600: No matching package to install: 'python3-pytest-httpbin' first. When filing requests could you mention the name in the bug title. It helps me keep better track of which bug is which. ;) Do you want to file requests for those 4? or perhaps some/all of them are already filed? #1836150 NEW - Fabian Affolter - Please provide a EL8 build #1815847 ASSIGNED - Gwyn Ciesla - please, provide epel8 update #1815843 NEW - Pierre-YvesChibon - please, provide epel8 update #1815852 NEW - Adam Williamson - python-pytest-httpbin: provide epel8 update So, lets add blocks on all those 4 and we can do this one when they are done. :)
Thank you, Kevin!
*** Bug 1815857 has been marked as a duplicate of this bug. ***
just wanted to mention that "python3-boto" might be an optional dependency (at least for vcrpy itself). I see that the code also supports "boto" but if that module is not available it'll just skip the patching/test.
Yeah, although on the other side, new python-vcrpy has added httpx support, so python3-httpx needed for that.
I've been looking into this since is the last blocker to get fedmsg into EPEL8 (and in consequence, for getting mbs into EPEL8) I tried to build the branch on EPEL9 (v4.1.1), but it fails because pyproject-rpm-macros are not available on EPEL8. Then I started from the previous commit (since the latest commit on that branch is the one that brings pyproject-rpm-macros into the EPEL9 branch [0]) and remove the python-boto BuildRequirement [1] as Felix mentioned and noticed that it builds fine [2]. Also this version is good enough to at least to build fedmsg tests on EPEL8 [3]. Would it be ok to just package version 4.1.1 into EPEL8? I could send a PR, but I would need to branch from the F36 branch for it to work. [0] https://src.fedoraproject.org/rpms/python-vcrpy/c/671bca9e866186dc21ae9314d8876e197fe4c17d?branch=epel9 [1] https://src.fedoraproject.org/fork/dherrera/rpms/python-vcrpy/c/4d6520aa3316a3d2a5159dba016c517f5942005a?branch=epel8 [2] https://koji.fedoraproject.org/koji/taskinfo?taskID=98162495 [3] https://copr.fedorainfracloud.org/coprs/dherrera/mbs-epel8/builds/
Branch added. Thanks for digging into this.
FEDORA-EPEL-2023-0c9e522b34 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-0c9e522b34
FEDORA-EPEL-2023-0c9e522b34 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-0c9e522b34 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2023-0c9e522b34 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.