Bug 2341540 - widelands: FTBFS in Fedora rawhide/f42
Summary: widelands: FTBFS in Fedora rawhide/f42
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: widelands
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Hanecak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F42FTBFS
TreeView+ depends on / blocked
 
Reported: 2025-01-22 22:19 UTC by Fedora Release Engineering
Modified: 2025-02-25 02:33 UTC (History)
3 users (show)

Fixed In Version: widelands-1.2.1-1.fc40 widelands-1.2.1-1.fc41
Clone Of:
Environment:
Last Closed: 2025-02-25 02:22:32 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (32.00 KB, text/plain)
2025-01-22 22:19 UTC, Fedora Release Engineering
no flags Details
root.log (32.00 KB, text/plain)
2025-01-22 22:19 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

Description Fedora Release Engineering 2025-01-22 22:19:55 UTC
widelands failed to build from source in Fedora rawhide/f42

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


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_42_Mass_Rebuild
Please fix widelands 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,
widelands will be orphaned. Before branching of Fedora 43,
widelands 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:19:58 UTC
Created attachment 2073143 [details]
build.log

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

Comment 2 Fedora Release Engineering 2025-01-22 22:19:59 UTC
Created attachment 2073144 [details]
root.log

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

Comment 3 Fedora Release Engineering 2025-01-22 22:20:01 UTC
Created attachment 2073145 [details]
state.log

Comment 4 Fedora Update System 2025-02-16 18:39:43 UTC
FEDORA-2025-04d90f5cf6 (widelands-1.2.1-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-04d90f5cf6

Comment 5 Fedora Update System 2025-02-16 18:40:05 UTC
FEDORA-2025-c82ae2a785 (widelands-1.2.1-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-c82ae2a785

Comment 6 Fedora Update System 2025-02-17 02:05:26 UTC
FEDORA-2025-04d90f5cf6 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-04d90f5cf6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-04d90f5cf6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2025-02-17 02:22:35 UTC
FEDORA-2025-c82ae2a785 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-c82ae2a785`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c82ae2a785

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2025-02-25 02:22:32 UTC
FEDORA-2025-04d90f5cf6 (widelands-1.2.1-1.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2025-02-25 02:33:16 UTC
FEDORA-2025-c82ae2a785 (widelands-1.2.1-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.


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