Bug 1605838 - python-pp: FTBFS in Fedora rawhide
Summary: python-pp: FTBFS in Fedora rawhide
Alias: None
Product: Fedora
Classification: Fedora
Component: python-pp
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Steve Milner
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: 1585626 F29FTBFS
TreeView+ depends on / blocked
Reported: 2018-07-20 17:14 UTC by Mohan Boddu
Modified: 2018-07-29 21:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-07-29 21:57:08 UTC

Attachments (Terms of Use)
build.log (3.43 KB, text/plain)
2018-07-20 17:14 UTC, Mohan Boddu
no flags Details
root.log (32.00 KB, text/plain)
2018-07-20 17:14 UTC, Mohan Boddu
no flags Details
state.log (631 bytes, text/plain)
2018-07-20 17:14 UTC, Mohan Boddu
no flags Details

Description Mohan Boddu 2018-07-20 17:14:16 UTC
python-pp failed to build from source in Fedora rawhide


For details on the mass rebuild see:

Please fix python-pp 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-pp will be orphaned. Before branching of Fedora 30,
python-pp will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:

Comment 1 Mohan Boddu 2018-07-20 17:14:23 UTC
Created attachment 1466621 [details]

Comment 2 Mohan Boddu 2018-07-20 17:14:27 UTC
Created attachment 1466622 [details]

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

Comment 3 Mohan Boddu 2018-07-20 17:14:30 UTC
Created attachment 1466623 [details]

Comment 4 Steve Milner 2018-07-20 17:54:32 UTC
python-pp does not look like it has plans to support python 3 and currently hard requires python 2. This package may need to be retired.

Comment 5 Igor Gnatenko 2018-07-29 21:57:08 UTC
There has been at least one successfull build after mass rebuild.

python-pp-1.6.0-16.fc29: https://koji.fedoraproject.org/koji/buildinfo?buildID=1122729

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