Bug 1605546 - pygobject3: FTBFS in Fedora rawhide
Summary: pygobject3: FTBFS in Fedora rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: pygobject3
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Colin Walters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1585626 F29FTBFS
TreeView+ depends on / blocked
 
Reported: 2018-07-20 15:56 UTC by Mohan Boddu
Modified: 2018-08-13 10:32 UTC (History)
4 users (show)

Fixed In Version: pygobject3-3.29.2-1.fc29
Clone Of:
Environment:
Last Closed: 2018-08-13 10:32:31 UTC
Type: ---
Embargoed:


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

Description Mohan Boddu 2018-07-20 15:56:43 UTC
pygobject3 failed to build from source in Fedora rawhide

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


For details on the mass rebuild see:

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

Comment 2 Mohan Boddu 2018-07-20 15:56:52 UTC
Created attachment 1465818 [details]
root.log

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

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

Comment 4 Kalev Lember 2018-08-13 10:32:31 UTC
Thanks, fixed in pygobject3-3.29.2-1.fc29


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