dnf install python3-scrapy fails in fedora 39 Reproducible: Always Steps to Reproduce: 1.dnf install python3-scrapy Actual Results: nf install python3-scrapy Last metadata expiration check: 1:10:09 ago on ??? 18 ??? 2023 06:37:18 ?? EET. ??????: Problem: conflicting requests - nothing provides (python3.12dist(twisted) < 23.8~~ with python3.12dist(twisted) >= 18.9) needed by python3-scrapy-2.10.1-1.fc39.noarch from fedora (try to add '--skip-broken' to skip uninstallable packages) Expected Results: To install python3-scrapy
FEDORA-2024-c27b82d702 (python-scrapy-2.11.2-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-c27b82d702
FEDORA-2024-0bd3b1212e (python-scrapy-2.11.2-1.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-0bd3b1212e
FEDORA-2024-c27b82d702 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-c27b82d702` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-c27b82d702 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-0bd3b1212e has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-0bd3b1212e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-0bd3b1212e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-c27b82d702 (python-scrapy-2.11.2-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-0bd3b1212e (python-scrapy-2.11.2-1.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.