Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1923285 - libcommuni: FTBFS in Fedora rawhide/f34
Summary: libcommuni: FTBFS in Fedora rawhide/f34
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: libcommuni
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Artem
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F34FTBFS
TreeView+ depends on / blocked
 
Reported: 2021-02-01 16:23 UTC by Fedora Release Engineering
Modified: 2021-02-19 05:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-19 05:15:42 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (32.00 KB, text/plain)
2021-02-01 16:23 UTC, Fedora Release Engineering 		no flags Details
root.log (32.00 KB, text/plain)
2021-02-01 16:23 UTC, Fedora Release Engineering 		no flags Details
state.log (981 bytes, text/plain)
2021-02-01 16:23 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2021-02-01 16:23:35 UTC 
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/
Comment 1 Fedora Release Engineering 2021-02-01 16:23:37 UTC 
Created attachment 1752931 [details]
build.log

file build.log too big, will only attach last 32768 bytes
Comment 2 Fedora Release Engineering 2021-02-01 16:23:38 UTC 
Created attachment 1752932 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Fedora Release Engineering 2021-02-01 16:23:39 UTC 
Created attachment 1752933 [details]
state.log
Comment 4 Ben Cotton 2021-02-09 15:45:58 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.
Comment 5 Fedora Release Engineering 2021-02-14 04:22:52 UTC 
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
Comment 6 Jeff Law 2021-02-19 05:15:42 UTC 
Seems to building/testing fine now.
Comment 7 Artem 2021-02-19 05:24:12 UTC 
@Jeff thanks a lot. Have no time even to tinker now with package.
Comment 8 Jeff Law 2021-02-19 05:30:18 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.