Bug 1800298 - ProDy: FTBFS in Fedora rawhide/f32
Summary: ProDy: FTBFS in Fedora rawhide/f32
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: ProDy
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Antonio T. (sagitter)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1800299
Blocks: F32FTBFS
TreeView+ depends on / blocked
 
Reported: 2020-02-06 20:29 UTC by Fedora Release Engineering
Modified: 2020-02-07 15:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-07 15:54:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (1.20 KB, text/plain)
2020-02-06 20:29 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2020-02-06 20:29 UTC, Fedora Release Engineering
no flags Details
state.log (829 bytes, text/plain)
2020-02-06 20:29 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2020-02-06 20:29:17 UTC
ProDy failed to build from source in Fedora rawhide/f32

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild
Please fix ProDy 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,
ProDy will be orphaned. Before branching of Fedora 33,
ProDy 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 Fedora Release Engineering 2020-02-06 20:29:20 UTC
Created attachment 1661511 [details]
build.log

Comment 2 Fedora Release Engineering 2020-02-06 20:29:22 UTC
Created attachment 1661512 [details]
root.log

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

Comment 3 Fedora Release Engineering 2020-02-06 20:29:23 UTC
Created attachment 1661513 [details]
state.log


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