Bug 1735004 - carto: FTBFS in Fedora rawhide/f31
Summary: carto: FTBFS in Fedora rawhide/f31
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: carto
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F31FTBFS 1732841
TreeView+ depends on / blocked
 
Reported: 2019-07-31 17:56 UTC by Fedora Release Engineering
Modified: 2019-08-01 08:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-01 08:45:07 UTC


Attachments (Terms of Use)
build.log (19.54 KB, text/plain)
2019-07-31 17:56 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2019-07-31 17:56 UTC, Fedora Release Engineering
no flags Details
state.log (621 bytes, text/plain)
2019-07-31 17:56 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2019-07-31 17:56:38 UTC
carto failed to build from source in Fedora rawhide/f31

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
Please fix carto 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,
carto will be orphaned. Before branching of Fedora 32,
carto 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-07-31 17:56:40 UTC
Created attachment 1595540 [details]
build.log

Comment 2 Fedora Release Engineering 2019-07-31 17:56:43 UTC
Created attachment 1595543 [details]
root.log

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

Comment 3 Fedora Release Engineering 2019-07-31 17:56:44 UTC
Created attachment 1595546 [details]
state.log


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