bolzplatz2006 failed to build from source in Fedora rawhide/f43 https://koji.fedoraproject.org/koji/taskinfo?taskID=135159583 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_43_Mass_Rebuild Please fix bolzplatz2006 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, bolzplatz2006 will be orphaned. Before branching of Fedora 44, bolzplatz2006 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 2098877 [details] build.log file build.log too big, will only attach last 32768 bytes
Created attachment 2098878 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 2098879 [details] state.log
I plan to fix these FTBFS issues as soon as I can make some time for it, moving to assigned.
FEDORA-2025-4308b59552 (bolzplatz2006-1.0.3-64.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2025-4308b59552
FEDORA-2025-4308b59552 (bolzplatz2006-1.0.3-64.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-5e08a2a9c6 (bolzplatz2006-1.0.3-64.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-5e08a2a9c6
FEDORA-2025-5e08a2a9c6 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-5e08a2a9c6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-5e08a2a9c6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-5e08a2a9c6 (bolzplatz2006-1.0.3-64.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.