Bug 1605714 - python-gevent-socketio: FTBFS in Fedora rawhide
Summary: python-gevent-socketio: FTBFS in Fedora rawhide
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-gevent-socketio
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Runge
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F29FTBFS
TreeView+ depends on / blocked
 
Reported: 2018-07-20 16:38 UTC by Mohan Boddu
Modified: 2018-07-23 07:23 UTC (History)
1 user (show)

Fixed In Version: python-gevent-socketio-0.3.6-9.fc29
Clone Of:
Environment:
Last Closed: 2018-07-23 07:23:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (3.67 KB, text/plain)
2018-07-20 16:38 UTC, Mohan Boddu
no flags Details
root.log (32.00 KB, text/plain)
2018-07-20 16:38 UTC, Mohan Boddu
no flags Details
state.log (679 bytes, text/plain)
2018-07-20 16:38 UTC, Mohan Boddu
no flags Details

Description Mohan Boddu 2018-07-20 16:38:21 UTC
python-gevent-socketio failed to build from source in Fedora rawhide

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild
Please fix python-gevent-socketio 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,
python-gevent-socketio will be orphaned. Before branching of Fedora 30,
python-gevent-socketio 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 16:38:27 UTC
Created attachment 1466257 [details]
build.log

Comment 2 Mohan Boddu 2018-07-20 16:38:30 UTC
Created attachment 1466258 [details]
root.log

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

Comment 3 Mohan Boddu 2018-07-20 16:38:32 UTC
Created attachment 1466259 [details]
state.log


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