Bug 1863706 - pybind11: FTBFS in Fedora rawhide/f33
Summary: pybind11: FTBFS in Fedora rawhide/f33
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: pybind11
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Susi Lehtola
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F33FTBFS
TreeView+ depends on / blocked
 
Reported: 2020-08-03 17:13 UTC by Fedora Release Engineering
Modified: 2020-08-05 12:08 UTC (History)
1 user (show)

Fixed In Version: pybind11-2.5.0-5.fc33
Clone Of:
Environment:
Last Closed: 2020-08-05 12:08:21 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (1.20 KB, text/plain)
2020-08-03 17:13 UTC, Fedora Release Engineering 		no flags Details
root.log (32.00 KB, text/plain)
2020-08-03 17:13 UTC, Fedora Release Engineering 		no flags Details
state.log (832 bytes, text/plain)
2020-08-03 17:13 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2020-08-03 17:13:39 UTC 
pybind11 failed to build from source in Fedora rawhide/f33

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
Please fix pybind11 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,
pybind11 will be orphaned. Before branching of Fedora 34,
pybind11 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 17:13:41 UTC 
Created attachment 1704638 [details]
build.log
Comment 2 Fedora Release Engineering 2020-08-03 17:13:42 UTC 
Created attachment 1704639 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Fedora Release Engineering 2020-08-03 17:13:43 UTC 
Created attachment 1704640 [details]
state.log
Note You need to log in before you can comment on or make changes to this bug.