dwarves failed to build from source in Fedora rawhide/f33 https://koji.fedoraproject.org/koji/taskinfo?taskID=47942770 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild Please fix dwarves 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, dwarves will be orphaned. Before branching of Fedora 34, dwarves will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://fedoraproject.org/wiki/Fails_to_build_from_source
Created attachment 1703997 [details] build.log
Created attachment 1703998 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 1703999 [details] state.log
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
I've submitted PR to both Fedora 33 and Fedora Rawhide. https://src.fedoraproject.org/rpms/dwarves/pull-request/1 https://src.fedoraproject.org/rpms/dwarves/pull-request/2 Note, `fedpkg build` and `fedpkg update` needed after merging Fedora 33 PR, as I don't have permission there.
FEDORA-2020-fd863d55c0 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-fd863d55c0
New builds awaiting user's karma: dwarves-1.17-4.fc33: https://bodhi.fedoraproject.org/updates/FEDORA-2020-fd863d55c0 dwarves-1.17-4.fc34: https://bodhi.fedoraproject.org/updates/FEDORA-2020-83adfcc633
FEDORA-2020-fd863d55c0 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-fd863d55c0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-fd863d55c0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-fd863d55c0 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.