Bug 1605542 - pyfribidi: FTBFS in Fedora rawhide
Summary: pyfribidi: FTBFS in Fedora rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: pyfribidi
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: F29FTBFS 1585626
TreeView+ depends on / blocked
 
Reported: 2018-07-20 15:55 UTC by Mohan Boddu
Modified: 2018-08-09 10:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-09 10:11:36 UTC


Attachments (Terms of Use)
build.log (3.86 KB, text/plain)
2018-07-20 15:55 UTC, Mohan Boddu
no flags Details
root.log (32.00 KB, text/plain)
2018-07-20 15:55 UTC, Mohan Boddu
no flags Details
state.log (635 bytes, text/plain)
2018-07-20 15:55 UTC, Mohan Boddu
no flags Details

Description Mohan Boddu 2018-07-20 15:55:37 UTC
pyfribidi failed to build from source in Fedora rawhide

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
Please fix pyfribidi 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,
pyfribidi will be orphaned. Before branching of Fedora 30,
pyfribidi 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:55:44 UTC
Created attachment 1465808 [details]
build.log

Comment 2 Mohan Boddu 2018-07-20 15:55:47 UTC
Created attachment 1465809 [details]
root.log

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

Comment 3 Mohan Boddu 2018-07-20 15:55:50 UTC
Created attachment 1465810 [details]
state.log

Comment 4 Hans de Goede 2018-08-09 10:11:36 UTC
Fixed in pyfribidi-0.11.0-17.fc29, closing.


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