Your message dated Fri, 13 Feb 2026 22:19:15 +0000
with message-id <[email protected]>
and subject line Bug#1127236: fixed in metabat 2.18-2
has caused the Debian Bug report #1127236,
regarding metabat: 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.)


-- 
1127236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127236
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:metabat
Version: 2.18-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: metabat
Source-Version: 2.18-2
Done: Andreas Tille <[email protected]>

We believe that the bug you reported is fixed in the latest version of
metabat, 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.
Andreas Tille <[email protected]> (supplier of updated metabat 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: Fri, 13 Feb 2026 22:53:06 +0100
Source: metabat
Architecture: source
Version: 2.18-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 
<[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1127236
Changes:
 metabat (2.18-2) unstable; urgency=medium
 .
   * Do not Build-Depend libboost-system-dev
     Closes: #1127236
   * cme fix dpkg-control
Checksums-Sha1:
 7d620432a79dd6bd54cd6be4356ceac5383dc88a 2189 metabat_2.18-2.dsc
 7e8fb95c09d7d17e3aeb7e9bf350ed3cd1a79c82 9184 metabat_2.18-2.debian.tar.xz
 019545f21b408dd695261e41de88f2079f88bd94 9982 metabat_2.18-2_amd64.buildinfo
Checksums-Sha256:
 45804cc936ade655248a817d59d1ac609ebaefa6dd30210aa7cc6cf322b5b2fb 2189 
metabat_2.18-2.dsc
 a42f8726fac009cf20ff6148b356a2d70752fcebe8ae6e7b6d81d384eb0ed3a2 9184 
metabat_2.18-2.debian.tar.xz
 a7a3b409d275bf517d66b8df8ed37a270c9a758643a7004fa4daa31ddbd907a7 9982 
metabat_2.18-2_amd64.buildinfo
Files:
 cab08ecbd4b9753b840a80a6e3a8ab70 2189 science optional metabat_2.18-2.dsc
 5c9e5ca9a5da754085de5e813c793564 9184 science optional 
metabat_2.18-2.debian.tar.xz
 a833c12dea6998e959dc80a5125965ea 9982 science optional 
metabat_2.18-2_amd64.buildinfo

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

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmmPnjoRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEHgRAAjh0hE1gfHZ5LD4o9PdiCmdM+9iOLvD0q
affA0sfEM7N9Q4Encs0UgVwrKeIhZukmdnJtcqtOE9T6Xj4MzGQoUyVQ81+4P2uf
tXgDQMpYyBERbFn56HIq8VYhx7ewTRJKQ9LXwYbpl1S8q/0GfXb8yGwBpx0ONKCn
1nHYZWFOZvgs/71JT41DH61/4IRlwYMXNaGQCqL3vdAGkgFuCKLIccC2+OLawuFv
2NZWY820Ik+GgbYd6PdGK53SUq125NKpUnGIX7IfPCQb5CozpGV2LsUEDdCXOoLX
B/l08guoErIlVi69dBWhOcTp4GGahE7tBjXTvvNDJ6dLz9bj2PPT6O+9dA2F0NxD
jm6HLHIdfbblE1tKth8wys5AAD3UHK0DicAc0sN5oyPRT+bKHezXbleOXeQCdOjL
3cuYrV/E9EnY+49D6weyiUlglkIZMnsaH0J7iPNkDgppZwFpGGnND8jdH83WseJa
I72EYB2UJrt8oYJPTpeMNh9+TIwX2Zs919D77O6tjvFIiSiP8dStGoWfevV/vba8
aomI3uZ5IP7wwBlThUMTYweqVq6CLIbXEqbiGd/kedMFujIy7amiOmgGBoNXbRdu
ql5/IJ4oWT0BM6cV6oCFwJ1G1MemAoFBw2Tvf5M0K3N2tJT1SdUGi3rNNtY82j89
NPgluewO0nE=
=ICCc
-----END PGP SIGNATURE-----

Attachment: pgpTqaKJH_tHv.pgp
Description: PGP signature


--- End Message ---

Reply via email to