Bug 1736945 - vdrift: FTBFS in Fedora rawhide/f31
Summary: vdrift: FTBFS in Fedora rawhide/f31
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: vdrift
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F31FTBFS 1732841
TreeView+ depends on / blocked
 
Reported: 2019-08-02 09:41 UTC by Fedora Release Engineering
Modified: 2019-08-05 22:26 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-03 18:19:56 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (10.06 KB, text/plain)
2019-08-02 09:41 UTC, Fedora Release Engineering 		no flags Details
root.log (32.00 KB, text/plain)
2019-08-02 09:41 UTC, Fedora Release Engineering 		no flags Details
state.log (633 bytes, text/plain)
2019-08-02 09:41 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2019-08-02 09:41:38 UTC 
vdrift failed to build from source in Fedora rawhide/f31

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
Please fix vdrift 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,
vdrift will be orphaned. Before branching of Fedora 32,
vdrift 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 2019-08-02 09:41:41 UTC 
Created attachment 1599783 [details]
build.log
Comment 2 Fedora Release Engineering 2019-08-02 09:41:43 UTC 
Created attachment 1599784 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Fedora Release Engineering 2019-08-02 09:41:45 UTC 
Created attachment 1599785 [details]
state.log
Note You need to log in before you can comment on or make changes to this bug.