Hi, Please branch and build python3-aiohttp in epel10. It will require this pull request to build fine: https://src.fedoraproject.org/rpms/python-aiohttp/pull-request/43 Cheers, Romain
Bump. This is blocking certbot in EPEL10 (through a chain of deps).
I’m happy to help branch and build this, but please note the missing dependencies blocking this bug. Someone (not me) has to take responsibility for getting those branched and built first. Additionally, aiohttp upstream has been in 3.11.x for some time, with 3.11.11 as the latest release. The primary maintainer of python-aiohttp in Fedora started work on that by uploading a new dependency, python-propcache, for review in bug 2318349. It would be great to get python-aiohttp up to date before branching since it has historically had reasonably regular security-related fixes.
*** Bug 2345191 has been marked as a duplicate of this bug. ***
In https://src.fedoraproject.org/rpms/python-aiohttp/pull-request/50, I conditionalized the BuildRequires and integration tests for gunicorn (bug 2331004) and uvloop (bug 2332434). That leaves only yarl (bug 2345826) and propcache (bug 2345872) as hard blockers. In a local mock build on EPEL10 with the above PR and with the above, there are still a couple of EPEL10-specific test failures that I don’t fully understand: =================================== FAILURES =================================== ___________________ test_empty_header_name[c-parser-pyloop] ____________________ [gw1] linux -- Python 3.12.9 /usr/bin/python3 parser = <aiohttp._http_parser.HttpRequestParser object at 0x7f0f45c66560> def test_empty_header_name(parser) -> None: text = b"GET /test HTTP/1.1\r\n:test\r\n\r\n" > with pytest.raises(http_exceptions.BadHttpMessage): E Failed: DID NOT RAISE <class 'aiohttp.http_exceptions.BadHttpMessage'> parser = <aiohttp._http_parser.HttpRequestParser object at 0x7f0f45c66560> text = b'GET /test HTTP/1.1\r\n:test\r\n\r\n' tests/test_http_parser.py:672: Failed _ test_invalid_header_spacing[c-parser-pyloop-pre-empty-post-empty-name-empty] _ [gw10] linux -- Python 3.12.9 /usr/bin/python3 parser = <aiohttp._http_parser.HttpRequestParser object at 0x7f8670d2a400> pad1 = b'', pad2 = b'', hdr = b'' @pytest.mark.parametrize("hdr", [b"", b"foo"], ids=["name-empty", "with-name"]) @pytest.mark.parametrize("pad2", _pad.keys(), ids=["post-" + n for n in _pad.values()]) @pytest.mark.parametrize("pad1", _pad.keys(), ids=["pre-" + n for n in _pad.values()]) def test_invalid_header_spacing(parser, pad1: bytes, pad2: bytes, hdr: bytes) -> None: text = b"GET /test HTTP/1.1\r\n%s%s%s: value\r\n\r\n" % (pad1, hdr, pad2) expectation = pytest.raises(http_exceptions.BadHttpMessage) if pad1 == pad2 == b"" and hdr != b"": # one entry in param matrix is correct: non-empty name, not padded expectation = nullcontext() > with expectation: E Failed: DID NOT RAISE <class 'aiohttp.http_exceptions.BadHttpMessage'> expectation = <_pytest.python_api.RaisesContext object at 0x7f8670fb4380> hdr = b'' pad1 = b'' pad2 = b'' parser = <aiohttp._http_parser.HttpRequestParser object at 0x7f8670d2a400> text = b'GET /test HTTP/1.1\r\n: value\r\n\r\n' tests/test_http_parser.py:666: Failed […] =========================== short test summary info ============================ […] XFAIL tests/test_connector.py::test_del_with_scheduled_cleanup[pyloop] XFAIL tests/test_client_functional.py::test_broken_connection[pyloop] XFAIL tests/test_http_parser.py::test_parse_uri_utf8[c-parser-pyloop] - reason: Not valid HTTP. Maybe update py-parser to reject later. XFAIL tests/test_http_parser.py::test_http_request_parser_utf8_request_line[c-parser-pyloop] - Regression test for Py parser. May match C behaviour later. XFAIL tests/test_http_parser.py::test_parse_unusual_request_line[c-parser-pyloop] - Regression test for Py parser. May match C behaviour later. FAILED tests/test_http_parser.py::test_empty_header_name[c-parser-pyloop] - F... FAILED tests/test_http_parser.py::test_invalid_header_spacing[c-parser-pyloop-pre-empty-post-empty-name-empty] ====== 2 failed, 3351 passed, 15 skipped, 5 xfailed, 5 warnings in 34.59s ====== These remind me of https://github.com/aio-libs/aiohttp/issues/8291, and I think they are related to the fact that the security fix in llhttp 9.2 was backported to llhttp 9.1.3 in EL10 rather than API/ABI-incompatibly updating llhttp. I am not up for the task of double-checking the backport or trying to understand the details of its interaction with python-aiohttp, so I guess skipping these two tests with a comment about the situation will be our only reasonable way forward.
*** Bug 2347375 has been marked as a duplicate of this bug. ***
Since https://src.fedoraproject.org/rpms/python-aiohttp/pull-request/50 is now merged to Rawhide, an EPEL10 branch could be based on the current state of Rawhide. I have conditionalized python-gunicorn (bug 2331004) and python-uvloop (bug 2332434) integration tests, so those are no longer blockers for EPEL10, but python-yarl (bug 2345826) and python-propcache (bug 2345872) are still missing hard dependencies. If those two were branched, then that would be enough for a successful python-aiohttp build.
My scratch build (https://koji.fedoraproject.org/koji/taskinfo?taskID=129656563, https://kojipkgs.fedoraproject.org/work/tasks/6579/129656579/root.log) seems to show that only python-yarl is needed (In reply to Ben Beasley from comment #6) > Since https://src.fedoraproject.org/rpms/python-aiohttp/pull-request/50 is > now merged to Rawhide, an EPEL10 branch could be based on the current state > of Rawhide. > > I have conditionalized python-gunicorn (bug 2331004) and python-uvloop (bug > 2332434) integration tests, so those are no longer blockers for EPEL10, but > python-yarl (bug 2345826) and python-propcache (bug 2345872) are still > missing hard dependencies. If those two were branched, then that would be > enough for a successful python-aiohttp build. Are you sure python-propcache is still needed? My scratch build (https://koji.fedoraproject.org/koji/taskinfo?taskID=129656563, https://kojipkgs.fedoraproject.org/work/tasks/6579/129656579/root.log) is only complaining about python-yarl.
(In reply to Kaleb KEITHLEY from comment #7) > My scratch build > (https://koji.fedoraproject.org/koji/taskinfo?taskID=129656563, > https://kojipkgs.fedoraproject.org/work/tasks/6579/129656579/root.log) > seems to show that only python-yarl is needed (In reply to Ben Beasley from > comment #6) > > Since https://src.fedoraproject.org/rpms/python-aiohttp/pull-request/50 is > > now merged to Rawhide, an EPEL10 branch could be based on the current state > > of Rawhide. > > > > I have conditionalized python-gunicorn (bug 2331004) and python-uvloop (bug > > 2332434) integration tests, so those are no longer blockers for EPEL10, but > > python-yarl (bug 2345826) and python-propcache (bug 2345872) are still > > missing hard dependencies. If those two were branched, then that would be > > enough for a successful python-aiohttp build. > > Are you sure python-propcache is still needed? My scratch build > (https://koji.fedoraproject.org/koji/taskinfo?taskID=129656563, > https://kojipkgs.fedoraproject.org/work/tasks/6579/129656579/root.log) is > only complaining about python-yarl. My bad. I see that it's python-yarl requires python-propcache
(In reply to Kaleb KEITHLEY from comment #8) > > My bad. I see that it's python-yarl requires python-propcache Not that the distinction is terribly important, but both python-aiohttp -> python-yarl -> python-propcache and python-aiohttp -> python-propcache exist as dependency chains. See: https://github.com/aio-libs/aiohttp/blob/6f09c515993ce754f009428df55b28bb77d202a6/setup.cfg#L60-L61 https://github.com/aio-libs/yarl/blob/5862a36c1a228e28bd830eedb5c2ef2b39523657/setup.cfg#L70
I see, Fabian already branched python-propcache to EPEL10, https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-b53fd9d1bd, but didn’t get around to closing the bug. Then you are right that only python-yarl is missing now.
scratch build for epel10.1 https://koji.fedoraproject.org/koji/taskinfo?taskID=129681906
Ok, I see python-yarl was branched and built in https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-4f8708df9f, it went straight to stable due to karma, and a buildroot override https://bodhi.fedoraproject.org/overrides/python-yarl-1.18.3-1.el10_1 is active. I can branch, build, and maintain this as a python-packagers-sig member and frequent group co-maintainer of the package. I’m inclined to wait a day or so for python-yarl to actually appear in the repos rather than relying on the buildroot override. If you need this in EPEL10.0, you’ll have to get python-yarl built there as well.
(In reply to Ben Beasley from comment #12) > > If you need this in EPEL10.0, you’ll have to get python-yarl built there as > well. python-yarl is built in epel10.0. Please build for both epel10.0 and epel10(.1) Thanks
FEDORA-EPEL-2025-b92d9dd8c6 (python-aiohttp-3.11.13-1.el10_1) has been submitted as an update to Fedora EPEL 10.1. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-b92d9dd8c6
EPEL10.0 to follow after https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-9d18d75ba0 reaches stable.
FEDORA-EPEL-2025-b92d9dd8c6 has been pushed to the Fedora EPEL 10.1 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-b92d9dd8c6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-fc7b3dad18 (python-aiohttp-3.11.13-1.el10_0) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-fc7b3dad18
FEDORA-EPEL-2025-b92d9dd8c6 (python-aiohttp-3.11.13-1.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-fc7b3dad18 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-fc7b3dad18 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-fc7b3dad18 (python-aiohttp-3.11.13-1.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.