Bug 1604179 - gofed: FTBFS in Fedora rawhide
Summary: gofed: FTBFS in Fedora rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gofed
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jan Chaloupka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1585626 F29FTBFS
TreeView+ depends on / blocked
 
Reported: 2018-07-19 21:24 UTC by Mohan Boddu
Modified: 2018-07-29 15:31 UTC (History)
2 users (show)

Fixed In Version: gofed-1.0.0-0.20.rc1.fc29
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-29 15:31:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (32.00 KB, text/plain)
2018-07-19 21:24 UTC, Mohan Boddu
no flags Details
root.log (32.00 KB, text/plain)
2018-07-19 21:24 UTC, Mohan Boddu
no flags Details
state.log (639 bytes, text/plain)
2018-07-19 21:24 UTC, Mohan Boddu
no flags Details

Description Mohan Boddu 2018-07-19 21:24:03 UTC
gofed failed to build from source in Fedora rawhide

https://koji.fedoraproject.org/koji/taskinfo?taskID=28183344


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
Please fix gofed 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,
gofed will be orphaned. Before branching of Fedora 30,
gofed 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

Comment 1 Mohan Boddu 2018-07-19 21:24:10 UTC
Created attachment 1462444 [details]
build.log

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

Comment 2 Mohan Boddu 2018-07-19 21:24:15 UTC
Created attachment 1462445 [details]
root.log

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

Comment 3 Mohan Boddu 2018-07-19 21:24:18 UTC
Created attachment 1462446 [details]
state.log


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