Your message dated Fri, 06 Mar 2026 10:05:44 +0000
with message-id <[email protected]>
and subject line Bug#1127299: fixed in wesnoth-1.18 1:1.18.6-2
has caused the Debian Bug report #1127299,
regarding wesnoth-1.18: libboost-system-dev package is obsolete with boost 1.89 
and newer
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1127299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127299
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:wesnoth-1.18
Version: 1:1.18.6-1
Severity: important
Tags: sid forky
User: [email protected]
Usertags: boost1.90

This package either build-depends on libboost-system-dev or depends on it.

The boost system library was removed upstream in 1.89, and is empty since 1.69.
If this library is referenced in the build system, the library can just be
removed from the build system, and the package should continue to build
for any boost version newer than 1.69, including boost1.83 in Debian.

There is no need to wait until boost 1.90 becomes the default, the issue
can be addressed in unstable. Issues to check:

  - Remove libboost-system-dev in Depends and Build-Depends.

  - Adjust autopkg tests and test dependencies if needed.

  - Scan the build system if the library is used, and remove it
    from the build system. https://www.boost.org/releases/1.89.0/
    has a short paragraph how to do that for cmake.

boost1.90 is now available in unstable, and a boost-defaults
defaulting to 1.90 is available in experimental. Please also check
that the package builds with boost 1.90.

--- End Message ---
--- Begin Message ---
Source: wesnoth-1.18
Source-Version: 1:1.18.6-2
Done: Vincent Cheng <[email protected]>

We believe that the bug you reported is fixed in the latest version of
wesnoth-1.18, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Vincent Cheng <[email protected]> (supplier of updated wesnoth-1.18 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 05 Mar 2026 23:24:45 -0800
Source: wesnoth-1.18
Built-For-Profiles: noudeb
Architecture: source
Version: 1:1.18.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team <[email protected]>
Changed-By: Vincent Cheng <[email protected]>
Closes: 1127299
Changes:
 wesnoth-1.18 (1:1.18.6-2) unstable; urgency=medium
 .
   * Add patch to fix FTBFS with boost > 1.89. (Closes: #1127299)
     - Drop build-dep on libboost-system-dev.
Checksums-Sha1:
 dc0532274f81f47cd33be1d52cddbd22a5d20ccb 4300 wesnoth-1.18_1.18.6-2.dsc
 90f38402eb98e6483fcdd8fd2ab128c68d972be6 180320 
wesnoth-1.18_1.18.6-2.debian.tar.xz
Checksums-Sha256:
 596d39d43d3a9251e8913b525e2f250ebcafb8795af4aefc12e8eb788ca69966 4300 
wesnoth-1.18_1.18.6-2.dsc
 e56d3ea234743a58f0a29d556db9ebd9dd959034c259cb0f91e18ec560ea2c1b 180320 
wesnoth-1.18_1.18.6-2.debian.tar.xz
Files:
 00e40002be997245c6548565c8d7c5e9 4300 games optional wesnoth-1.18_1.18.6-2.dsc
 43d03daff05d10ed87a86d78b44e75dc 180320 games optional 
wesnoth-1.18_1.18.6-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE1TqBWjy3ZZr4guOVju3MG6ofMv8FAmmqg5oACgkQju3MG6of
Mv8F/RAA93SWpROOcrKKZ/4AQHLBOJJPa88JYy+U8LuuKrFEkHlK9yTKI9IQ7Kx2
m5WvXL5f1Olir0qf7NdCEkbxVCsIpOR9hFJ3RgGqt+zpzWfaj7uUq5Qf2D/XUNoV
uytYAA729B2LAS9eO88Kforld3xqlxOHIpziHjbQ3BC6j8CQYvmAE3zkjKWLiKEl
ReE7Nepuvf7Ux4KoCA023/E+2BKy54Jh3/C3iTIgqvjij8pjzv14nEetJIg1+q/0
u/3wKtfsCiHs6Is1ziOMiFZP7NhMbQfGRr7fL/EZiV0VbQ6q+U5DKYBFT6l3xxuD
HpxO7lS7AMuVF1gfSc8a+sAlsAtPHaMIm+FdXfFcevxasWrHVvGTapy/9cfwc7x1
TAZ1Q+XlfT9embjhg8f8uYdBPcwBMH2TqHoAv0tqUE/ospB9fnhNH5up5vYrYqcM
GQ8/Wh7VGbG4JBPMPCOYG7UIXpmgkaEII33uZ0xedCrDpwR1/IVKxd3c9Uc5xbpF
CTT6FPuVaz0P53cKd3+fO5OCERV2LHOEiRaSQeYiG6sLWzd1h6B+eKUqGq+rhTIT
5yckkPrbQqF3oU1gL91iEeaN/FwyGKEmu/QSPCuE06o+dki3Xjfq5t3iy0p8HU7P
BVtg7Y/YkvWDEE8VTfDwpidwkhIF525tNdRkR3ipkbhkLvOflqU=
=N9C4
-----END PGP SIGNATURE-----

Attachment: pgpK45j25tZ18.pgp
Description: PGP signature


--- End Message ---

Reply via email to