Bug 1605401 - peripety: FTBFS in Fedora rawhide
Summary: peripety: FTBFS in Fedora rawhide
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: peripety
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gris Ge
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F29FTBFS
TreeView+ depends on / blocked
 
Reported: 2018-07-20 15:13 UTC by Mohan Boddu
Modified: 2018-07-24 02:39 UTC (History)
1 user (show)

Fixed In Version: peripety-0.1.2-3.fc29
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-24 02:39:59 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (3.69 KB, text/plain)
2018-07-20 15:14 UTC, Mohan Boddu 		no flags Details
root.log (32.00 KB, text/plain)
2018-07-20 15:14 UTC, Mohan Boddu 		no flags Details
state.log (623 bytes, text/plain)
2018-07-20 15:14 UTC, Mohan Boddu 		no flags Details
View All

Description Mohan Boddu 2018-07-20 15:13:58 UTC 
peripety failed to build from source in Fedora rawhide

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
Please fix peripety 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,
peripety will be orphaned. Before branching of Fedora 30,
peripety 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-20 15:14:02 UTC 
Created attachment 1465386 [details]
build.log
Comment 2 Mohan Boddu 2018-07-20 15:14:05 UTC 
Created attachment 1465387 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Mohan Boddu 2018-07-20 15:14:09 UTC 
Created attachment 1465388 [details]
state.log
Comment 4 Gris Ge 2018-07-24 02:39:59 UTC 
Fixed.
Note You need to log in before you can comment on or make changes to this bug.