Fedora Account System
Red Hat Associate
Red Hat Customer
python-pytest-trio failed to build from source in Fedora rawhide/f40 https://koji.fedoraproject.org/koji/taskinfo?taskID=112397218 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_40_Mass_Rebuild Please fix python-pytest-trio at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, python-pytest-trio will be orphaned. Before branching of Fedora 41, python-pytest-trio will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
Created attachment 2013273 [details] build.log file build.log too big, will only attach last 32768 bytes
Created attachment 2013274 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 2013275 [details] state.log
FEDORA-2024-5d7a3093da (python-pytest-trio-0.8.0-7.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-5d7a3093da
FEDORA-2024-5d7a3093da (python-pytest-trio-0.8.0-7.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-6621d379f7 (python-pytest-trio-0.8.0-7.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-6621d379f7
FEDORA-2024-6621d379f7 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-6621d379f7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-6621d379f7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-6621d379f7 (python-pytest-trio-0.8.0-7.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.