Bug 2341541 - wimlib: FTBFS in Fedora rawhide/f42
Summary: wimlib: FTBFS in Fedora rawhide/f42
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: wimlib
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mohamed El Morabity
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F42FTBFS
TreeView+ depends on / blocked
 
Reported: 2025-01-22 22:20 UTC by Fedora Release Engineering
Modified: 2025-01-25 19:48 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-01-25 19:48:02 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (26.30 KB, text/plain)
2025-01-22 22:20 UTC, Fedora Release Engineering 		no flags Details
root.log (32.00 KB, text/plain)
2025-01-22 22:20 UTC, Fedora Release Engineering 		no flags Details
state.log (1.63 KB, text/plain)
2025-01-22 22:20 UTC, Fedora Release Engineering 		no flags Details
View All

Description Fedora Release Engineering 2025-01-22 22:20:02 UTC 
wimlib failed to build from source in Fedora rawhide/f42

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_42_Mass_Rebuild
Please fix wimlib 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,
wimlib will be orphaned. Before branching of Fedora 43,
wimlib will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
Comment 1 Fedora Release Engineering 2025-01-22 22:20:05 UTC 
Created attachment 2073146 [details]
build.log
Comment 2 Fedora Release Engineering 2025-01-22 22:20:07 UTC 
Created attachment 2073147 [details]
root.log

file root.log too big, will only attach last 32768 bytes
Comment 3 Fedora Release Engineering 2025-01-22 22:20:08 UTC 
Created attachment 2073148 [details]
state.log
Note You need to log in before you can comment on or make changes to this bug.