Hello, Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok). Your package (python-uvicorn) Fails To Install in Fedora 37: can't install python3-uvicorn+standard: - nothing provides python(abi) = 3.10 needed by python3-uvicorn+standard-0.15.0-2.fc36.noarch - nothing provides python3.10dist(pyyaml) >= 5.1 needed by python3-uvicorn+standard-0.15.0-2.fc36.noarch - nothing provides ((python3.10dist(uvloop) < 0.15 or python3.10dist(uvloop) > 0.15) with (python3.10dist(uvloop) < 0.15.1 or python3.10dist(uvloop) > 0.15.1) with python3.10dist(uvloop) >= 0.14) needed by python3-uvicorn+standard-0.15.0-2.fc36.noarch - nothing provides (python3.10dist(httptools) >= 0.2 with python3.10dist(httptools) < 0.3) needed by python3-uvicorn+standard-0.15.0-2.fc36.noarch - nothing provides python3.10dist(python-dotenv) >= 0.13 needed by python3-uvicorn+standard-0.15.0-2.fc36.noarch - nothing provides python3.10dist(websockets) >= 9.1 needed by python3-uvicorn+standard-0.15.0-2.fc36.noarch can't install python3-uvicorn: - nothing provides python(abi) = 3.10 needed by python3-uvicorn-0.15.0-2.fc36.noarch - nothing provides python3.10dist(click) >= 7 needed by python3-uvicorn-0.15.0-2.fc36.noarch - nothing provides python3.10dist(asgiref) >= 3.4 needed by python3-uvicorn-0.15.0-2.fc36.noarch - nothing provides python3.10dist(h11) >= 0.8 needed by python3-uvicorn-0.15.0-2.fc36.noarch If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem. If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks. P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. To reproduce, use the koji/local repo only, e.g. in mock: $ mock -r fedora-37-x86_64 --disablerepo='*' --enablerepo=local install python3-uvicorn+standard python3-uvicorn P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages Thanks!
This bugzilla is likely a fallout from the Python 3.11 rebuild. If your package (or some of the dependencies it has) failed to rebuild during the Python 3.11 rebuild, they now fail to install. To fix this, packages need to be rebuilt in Rawhide. We will slowly triage the bugzillas, but we'd appreciate your help. If you know this is blocked by an existing reported build failure or another package not yet rebuilt with Python 3.11, please mark it as such by using the "Depends On"/"Blocks" bugzilla fields. That will help us determine what failures to prioritize. If this is not Python 3.11 related, please remove the PYTHON3.11 blocking tracker. Thank you and sorry for the inconvenience. Let me know if you need any help.
Hello, This is the first reminder (step 3 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs). If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.
+ /usr/bin/pytest --verbose INTERNALERROR> Traceback (most recent call last): INTERNALERROR> File "/usr/lib/python3.11/site-packages/_pytest/main.py", line 264, in wrap_session INTERNALERROR> config._do_configure() INTERNALERROR> ^^^^^^^^^^^^^^^^^^^^^^ INTERNALERROR> File "/usr/lib/python3.11/site-packages/_pytest/config/__init__.py", line 995, in _do_configure INTERNALERROR> self.hook.pytest_configure.call_historic(kwargs=dict(config=self)) INTERNALERROR> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ INTERNALERROR> File "/usr/lib/python3.11/site-packages/pluggy/_hooks.py", line 277, in call_historic INTERNALERROR> res = self._hookexec(self.name, self.get_hookimpls(), kwargs, False) INTERNALERROR> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ INTERNALERROR> File "/usr/lib/python3.11/site-packages/pluggy/_manager.py", line 80, in _hookexec INTERNALERROR> return self._inner_hookexec(hook_name, methods, kwargs, firstresult) INTERNALERROR> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ INTERNALERROR> File "/usr/lib/python3.11/site-packages/pluggy/_callers.py", line 60, in _multicall INTERNALERROR> return outcome.get_result() INTERNALERROR> ^^^^^^^^^^^^^^^^^^^^ INTERNALERROR> File "/usr/lib/python3.11/site-packages/pluggy/_result.py", line 60, in get_result INTERNALERROR> raise ex[1].with_traceback(ex[2]) INTERNALERROR> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ INTERNALERROR> File "/usr/lib/python3.11/site-packages/pluggy/_callers.py", line 39, in _multicall INTERNALERROR> res = hook_impl.function(*args) INTERNALERROR> ^^^^^^^^^^^^^^^^^^^^^^^^^ INTERNALERROR> File "/usr/lib/python3.11/site-packages/pytest_asyncio/plugin.py", line 191, in pytest_configure INTERNALERROR> config.issue_config_time_warning(LEGACY_MODE, stacklevel=2) INTERNALERROR> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ INTERNALERROR> File "/usr/lib/python3.11/site-packages/_pytest/config/__init__.py", line 1342, in issue_config_time_warning INTERNALERROR> warnings.warn(warning, stacklevel=stacklevel) INTERNALERROR> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ INTERNALERROR> DeprecationWarning: The 'asyncio_mode' default value will change to 'strict' in future, please explicitly use 'asyncio_mode=strict' or 'asyncio_mode=auto' in pytest configuration file.
I’m going to add > -W 'default::DeprecationWarning' to the pytest arguments so that the deprecation warnings bubbling up from pytest_asyncio and httpx are not treated as errors. In general, I think failing on deprecation warnings is too strict for RPM building, although it’s appropriate for upstream CI. Once I do that, all the tests pass: =============================== warnings summary =============================== ../../../../usr/lib/python3.11/site-packages/pytest_asyncio/plugin.py:191 /usr/lib/python3.11/site-packages/pytest_asyncio/plugin.py:191: DeprecationWarning: The 'asyncio_mode' default value will change to 'strict' in future, please explicitly use 'asyncio_mode=strict' or 'asyncio_mode=auto' in pytest configuration file. config.issue_config_time_warning(LEGACY_MODE, stacklevel=2) ../../../../usr/lib/python3.11/site-packages/httpx/_models.py:1 /usr/lib/python3.11/site-packages/httpx/_models.py:1: DeprecationWarning: 'cgi' is deprecated and slated for removal in Python 3.13 import cgi -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html ======================= 348 passed, 2 warnings in 34.13s =======================
FEDORA-2022-4770b9051f has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-4770b9051f
FEDORA-2022-4770b9051f has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
Thanks for taking care of this Ben!