Bug 1734866 - glusterfs: FTBFS in Fedora rawhide/f31
Summary: glusterfs: FTBFS in Fedora rawhide/f31
Alias: None
Product: Fedora
Classification: Fedora
Component: glusterfs
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Kaleb KEITHLEY
QA Contact: Fedora Extras Quality Assurance
: 1735397 (view as bug list)
Depends On: 1733602
Blocks: F31FTBFS 1732841
TreeView+ depends on / blocked
Reported: 2019-07-31 16:04 UTC by Fedora Release Engineering
Modified: 2019-08-01 20:10 UTC (History)
8 users (show)

Fixed In Version: glusterfs-6.4-3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-08-01 20:10:03 UTC
Type: ---

Attachments (Terms of Use)
build.log (1.65 KB, text/plain)
2019-07-31 16:04 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2019-07-31 16:05 UTC, Fedora Release Engineering
no flags Details
state.log (475 bytes, text/plain)
2019-07-31 16:05 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2019-07-31 16:04:51 UTC
glusterfs failed to build from source in Fedora rawhide/f31


For details on the mass rebuild see:

Please fix glusterfs 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,
glusterfs will be orphaned. Before branching of Fedora 32,
glusterfs will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:

Comment 1 Fedora Release Engineering 2019-07-31 16:04:54 UTC
Created attachment 1595169 [details]

Comment 2 Fedora Release Engineering 2019-07-31 16:05:01 UTC
Created attachment 1595170 [details]

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2019-07-31 16:05:02 UTC
Created attachment 1595171 [details]

Comment 4 Kaleb KEITHLEY 2019-08-01 20:08:12 UTC
*** Bug 1735397 has been marked as a duplicate of this bug. ***

Comment 5 Kaleb KEITHLEY 2019-08-01 20:10:03 UTC
fixed in glusterfs-6.4-3

Note You need to log in before you can comment on or make changes to this bug.