Description of problem: Version-Release number of selected component (if applicable): python3-treq-18.6.0-5.fc34.noarch python3-twisted-21.2.0-2.fc35.noarch How reproducible: easily Steps to Reproduce: python3 -c 'import treq.client' Actual results: Traceback (most recent call last): File "<string>", line 1, in <module> File "/usr/lib/python3.9/site-packages/treq/__init__.py", line 5, in <module> from treq.api import head, get, post, put, patch, delete, request File "/usr/lib/python3.9/site-packages/treq/api.py", line 5, in <module> from treq.client import HTTPClient File "/usr/lib/python3.9/site-packages/treq/client.py", line 11, in <module> from twisted.python.compat import _PY3, unicode ImportError: cannot import name '_PY3' from 'twisted.python.compat' (unknown location) Expected results: Should import successfully Additional info: Fixed upstream already: https://github.com/twisted/treq/pull/290 The fix is included in the 20.9.0 release (see bug 1813778). This prevents the latest version of matrix-synapse from building.
This also prevents the current version of matrix-synapse from running.
Updating python3-treq to a build of 21.1.0 from rawhide for f34 fixes synapse.
Please update python-treq to 20.9.0 or newer for Fedora 34 so we can update matrix-synapse to its newest version.
FEDORA-2021-58cefb2bf4 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-58cefb2bf4
FEDORA-2021-58cefb2bf4 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-58cefb2bf4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-58cefb2bf4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-58cefb2bf4 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
*** Bug 1960256 has been marked as a duplicate of this bug. ***