Bug 1799151 - amora: FTBFS in Fedora rawhide/f32
Summary: amora: FTBFS in Fedora rawhide/f32
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: amora
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Filipe Rosset
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F32FTBFS
TreeView+ depends on / blocked
 
Reported: 2020-02-06 15:57 UTC by Fedora Release Engineering
Modified: 2020-02-11 03:27 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-11 03:27:59 UTC
Type: ---


Attachments (Terms of Use)
build.log (19.09 KB, text/plain)
2020-02-06 15:57 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2020-02-06 15:57 UTC, Fedora Release Engineering
no flags Details
state.log (954 bytes, text/plain)
2020-02-06 15:57 UTC, Fedora Release Engineering
no flags Details

Description Fedora Release Engineering 2020-02-06 15:57:35 UTC
amora failed to build from source in Fedora rawhide/f32

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild
Please fix amora 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,
amora will be orphaned. Before branching of Fedora 33,
amora 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 15:57:40 UTC
Created attachment 1658414 [details]
build.log

Comment 2 Fedora Release Engineering 2020-02-06 15:57:41 UTC
Created attachment 1658415 [details]
root.log

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

Comment 3 Fedora Release Engineering 2020-02-06 15:57:44 UTC
Created attachment 1658416 [details]
state.log


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