Your message dated Sun, 22 Mar 2026 11:19:24 +0000
with message-id <[email protected]>
and subject line Bug#1127289: fixed in trojan 1.16.0-1.2
has caused the Debian Bug report #1127289,
regarding trojan: 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.)


-- 
1127289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127289
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:trojan
Version: 1.16.0-1.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: trojan
Source-Version: 1.16.0-1.2
Done: Adrian Bunk <[email protected]>

We believe that the bug you reported is fixed in the latest version of
trojan, 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.
Adrian Bunk <[email protected]> (supplier of updated trojan 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, 20 Mar 2026 15:38:06 +0200
Source: trojan
Architecture: source
Version: 1.16.0-1.2
Distribution: unstable
Urgency: medium
Maintainer: GreaterFire <[email protected]>
Changed-By: Adrian Bunk <[email protected]>
Closes: 1127289
Changes:
 trojan (1.16.0-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS with Boost 1.90. (Closes: #1127289)
Checksums-Sha1:
 0efaaa1cbd78ece994246d0b01dfa14269caeec3 2055 trojan_1.16.0-1.2.dsc
 6eaf9aaa3b80eb312866fc42189f6fdc420c29c4 3392 trojan_1.16.0-1.2.debian.tar.xz
Checksums-Sha256:
 1e8ddd37d03b28ef5e259123974a5fa8e0ec68e6e652ad74b0a2d918c42ae636 2055 
trojan_1.16.0-1.2.dsc
 03a3a8fa8bff2d957640e2acb47ad399ad3f78794c64f6088e976b15864caa28 3392 
trojan_1.16.0-1.2.debian.tar.xz
Files:
 15dbc70922dbc5a821c3cb3fe8974691 2055 web optional trojan_1.16.0-1.2.dsc
 f3dad9eeeeb35fa6e89d70913d7ed9a3 3392 web optional 
trojan_1.16.0-1.2.debian.tar.xz

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

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmm9T8kACgkQiNJCh6LY
mLFfmRAAjodGdY25PX8+Heknx07EvCBx+HnPsaEm4NrKgp4FH8VA/HK/ntQhi12w
O9LG76fD2DIeOl+n4OAn27HtKyoTK0WwYj8mO5fKgQTww3/i2O3j2DoA6/fUWly9
H1YCkLJNjN0nYpqHpitZv09KhXgyC0WzteuRHQRLqLCIRHy8YQw5fssTd9O3Ehho
tsfjWdK0imgdtGuJTmdWYpY7ANJCkfWdugRs2XlwWHct06TcHLO6mo0Z0UbIw1oa
KhIvJnfr/fNp5zg3iImgPI/M2PTJgdTvjDCbKQ81A5Ot8mJO8+2AxkCTXdUGXFgi
2DcDsj8jIySgyGxIY69dT8Q+sT74mit2wd6vN1VHiCTQGNk+7Orr7Mg+doV/2UH1
Fm/to8Kii7TTG4obDnw3FK2QgBDwocbn0ssd7xSrdQrVTa+uI1l89/mIxMujaNFD
b+GLJFLJ/QHjqxXqNaVq7R8/nkHyKezCbTsYwJfl5mRhBeeAJrLxfO7RyoE7K8S6
eeoqLj2AwLXEptSr1Z9OE4kraXOHS1O+1CfJtnQyy0sC/01Aoam+bT1/52ppWz7b
fhXLWecwS0uhQzQEnsatXZgG9XqjhHhaYEcMhATZdnmip9AiuFTvzQo9TT9uf6n/
9oOI/mzLRzJJV16GrmQEv5llPk6Z1/rxbrZwU0kwy6Dc9uwH+80=
=SQrc
-----END PGP SIGNATURE-----

Attachment: pgpNf3p6SkBZ_.pgp
Description: PGP signature


--- End Message ---

Reply via email to