Bug 1605361 - pachi: FTBFS in Fedora rawhide
Summary: pachi: FTBFS in Fedora rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: pachi
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1551327 F29FTBFS
TreeView+ depends on / blocked
 
Reported: 2018-07-20 15:02 UTC by Mohan Boddu
Modified: 2018-08-02 20:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-02 20:32:10 UTC
Type: ---
Embargoed:

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

Description Mohan Boddu 2018-07-20 15:02:42 UTC 
pachi failed to build from source in Fedora rawhide

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


For details on the mass rebuild see:

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

file root.log too big, will only attach last 32768 bytes
Comment 3 Mohan Boddu 2018-07-20 15:02:58 UTC 
Created attachment 1465280 [details]
state.log
Comment 4 Hans de Goede 2018-08-02 20:32:10 UTC 
Fixed in pachi-1.0-27.fc29, closing.
Note You need to log in before you can comment on or make changes to this bug.