Bug 1865398 - rpy: FTBFS in Fedora rawhide/f33
Summary: rpy: FTBFS in Fedora rawhide/f33
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: rpy
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: José Matos
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F33FTBFS
TreeView+ depends on / blocked
 
Reported: 2020-08-03 21:02 UTC by Fedora Release Engineering
Modified: 2020-08-05 12:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-05 12:07:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (1.18 KB, text/plain)
2020-08-03 21:02 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2020-08-03 21:02 UTC, Fedora Release Engineering
no flags Details
state.log (804 bytes, text/plain)
2020-08-03 21:02 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2020-08-03 21:02:47 UTC
rpy failed to build from source in Fedora rawhide/f33

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
Please fix rpy 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,
rpy will be orphaned. Before branching of Fedora 34,
rpy 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-08-03 21:02:49 UTC
Created attachment 1709360 [details]
build.log

Comment 2 Fedora Release Engineering 2020-08-03 21:02:50 UTC
Created attachment 1709361 [details]
root.log

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

Comment 3 Fedora Release Engineering 2020-08-03 21:02:51 UTC
Created attachment 1709362 [details]
state.log


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