Bug 2429734 - F44FailsToInstall: wesnoth, wesnoth-server
Summary: F44FailsToInstall: wesnoth, wesnoth-server
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: wesnoth
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F44FailsToInstall 2429148
TreeView+ depends on / blocked
 
Reported: 2026-01-14 19:09 UTC by Fedora Fails To Install
Modified: 2026-01-31 17:27 UTC (History)
3 users (show)

Fixed In Version: wesnoth-1.19.20-1.fc42 wesnoth-1.19.20-1.fc43
Clone Of:
Environment:
Last Closed: 2026-01-22 11:20:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github wesnoth wesnoth issues 10861 0 None open Build failure 1.19.19 on Boost 1.90.0 2026-01-15 18:03:00 UTC

Description Fedora Fails To Install 2026-01-14 19:09:55 UTC
Hello,

Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/

Your package (wesnoth) Fails To Install in Fedora 44:

can't install wesnoth:
  - nothing provides libboost_program_options.so.1.83.0()(64bit) needed by wesnoth-1.19.19-1.fc44.x86_64
  - nothing provides libboost_filesystem.so.1.83.0()(64bit) needed by wesnoth-1.19.19-1.fc44.x86_64
  - nothing provides libboost_iostreams.so.1.83.0()(64bit) needed by wesnoth-1.19.19-1.fc44.x86_64
  - nothing provides libboost_locale.so.1.83.0()(64bit) needed by wesnoth-1.19.19-1.fc44.x86_64
  - nothing provides libboost_random.so.1.83.0()(64bit) needed by wesnoth-1.19.19-1.fc44.x86_64
  
can't install wesnoth-server:
  - nothing provides libboost_program_options.so.1.83.0()(64bit) needed by wesnoth-server-1.19.19-1.fc44.x86_64
  - nothing provides libboost_filesystem.so.1.83.0()(64bit) needed by wesnoth-server-1.19.19-1.fc44.x86_64
  - nothing provides libboost_iostreams.so.1.83.0()(64bit) needed by wesnoth-server-1.19.19-1.fc44.x86_64
  - nothing provides libboost_context.so.1.83.0()(64bit) needed by wesnoth-server-1.19.19-1.fc44.x86_64
  - nothing provides libboost_locale.so.1.83.0()(64bit) needed by wesnoth-server-1.19.19-1.fc44.x86_64
  - nothing provides libboost_coroutine.so.1.83.0()(64bit) needed by wesnoth-server-1.19.19-1.fc44.x86_64
  - nothing provides libboost_random.so.1.83.0()(64bit) needed by wesnoth-server-1.19.19-1.fc44.x86_64
  
If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.


If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks.


P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. To reproduce, use the koji/local repo only, e.g. in mock:

    $ mock -r fedora-44-x86_64 --config-opts mirrored=False install wesnoth wesnoth-server


P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages

Thanks!

Comment 1 Jonathan Wakely 2026-01-15 01:36:35 UTC
Needs a patch to build with boost 1.90.0

https://github.com/wesnoth/wesnoth/pull/10175/

Comment 2 Gwyn Ciesla 2026-01-15 18:00:11 UTC
That patch is already part of 1.19.19. I'll file a new issue.

Comment 3 Fedora Update System 2026-01-21 17:51:05 UTC
FEDORA-2026-873e9e24ea (wesnoth-1.19.20-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-873e9e24ea

Comment 4 Fedora Update System 2026-01-21 17:51:05 UTC
FEDORA-2026-2424535dba (wesnoth-1.19.20-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-2424535dba

Comment 5 Fedora Update System 2026-01-22 01:43:18 UTC
FEDORA-2026-2424535dba has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-2424535dba`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-2424535dba

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

Comment 6 Fedora Update System 2026-01-22 01:54:54 UTC
FEDORA-2026-873e9e24ea has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-873e9e24ea`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-873e9e24ea

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

Comment 7 Fedora Fails To Install 2026-01-22 11:20:52 UTC
Hello,

Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/

All subpackages of a package against which this bug was filled are now installable or removed from Fedora 44.

Thanks for taking care of it!

Comment 8 Fedora Update System 2026-01-31 17:09:09 UTC
FEDORA-2026-873e9e24ea (wesnoth-1.19.20-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2026-01-31 17:27:40 UTC
FEDORA-2026-2424535dba (wesnoth-1.19.20-1.fc43) has been pushed to the Fedora 43 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.