Fedora Account System
Red Hat Associate
Red Hat Customer
libcommuni failed to build from source in Fedora rawhide/f34 https://koji.fedoraproject.org/koji/taskinfo?taskID=60904941 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild Please fix libcommuni 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, libcommuni will be orphaned. Before branching of Fedora 35, libcommuni 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 1752931 [details] build.log file build.log too big, will only attach last 32768 bytes
Created attachment 1752932 [details] root.log file root.log too big, will only attach last 32768 bytes
Created attachment 1752933 [details] state.log
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
Dear Maintainer, your package has an open Fails To Build From Source bug for Fedora 34. Action is required from you. If you can fix your package to build, perform a build in koji, and either create an update in bodhi, or close this bug without creating an update, if updating is not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to acknowledge this. If you have already fixed this issue, please close this Bugzilla report. Following the policy for such packages [2], your package will be orphaned if this bug remains in NEW state more than 8 weeks (not sooner than 2021-03-29). A week before the mass branching of Fedora 35 according to the schedule [3], any packages not successfully rebuilt at least on Fedora 33 will be retired regardless of the status of this bug. [1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ [2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ [3] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html
Seems to building/testing fine now.
@Jeff thanks a lot. Have no time even to tinker now with package.
No problem. I'm primarily concerned with identifying potential GCC 11 issues and I'd marked libcommuni as needing further investigation to rule it in or out (a package testsuite failure like libcommuni had could easily be caused by a compiler bug). That investigation showed the package building & testing without issues now, so it was easy enough to spin an official build and close the BZ. It could have been a compiler bug that got fixed after the mass rebuild, a flakey test, etc. Ultimately I'm just happy it's working and we don't need to worry about it anymore from a compiler standpoint.