Bug 1800262 - wsjtx: FTBFS in Fedora rawhide/f32
Summary: wsjtx: FTBFS in Fedora rawhide/f32
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: wsjtx
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F32FTBFS
TreeView+ depends on / blocked
 
Reported: 2020-02-06 20:24 UTC by Fedora Release Engineering
Modified: 2020-02-10 18: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-02-10 18:07:46 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (63 bytes, text/plain)
2020-02-06 20:24 UTC, Fedora Release Engineering 		no flags Details
root.log (32.00 KB, text/plain)
2020-02-06 20:24 UTC, Fedora Release Engineering 		no flags Details
state.log (821 bytes, text/plain)
2020-02-06 20:24 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2020-02-06 20:24:32 UTC 
wsjtx failed to build from source in Fedora rawhide/f32

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild
Please fix wsjtx 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,
wsjtx will be orphaned. Before branching of Fedora 33,
wsjtx 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 20:24:34 UTC 
Created attachment 1661406 [details]
build.log
Comment 2 Fedora Release Engineering 2020-02-06 20:24:36 UTC 
Created attachment 1661407 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Fedora Release Engineering 2020-02-06 20:24:39 UTC 
Created attachment 1661408 [details]
state.log
Note You need to log in before you can comment on or make changes to this bug.