Your message dated Tue, 10 Mar 2026 20:33:38 +0000
with message-id <[email protected]>
and subject line Bug#1127270: fixed in ros-rospack 2.6.4-2
has caused the Debian Bug report #1127270,
regarding ros-rospack: 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.)


-- 
1127270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127270
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:ros-rospack
Version: 2.6.4-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: ros-rospack
Source-Version: 2.6.4-2
Done: Timo Röhling <[email protected]>

We believe that the bug you reported is fixed in the latest version of
ros-rospack, 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.
Timo Röhling <[email protected]> (supplier of updated ros-rospack 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: Tue, 10 Mar 2026 21:30:08 +0100
Source: ros-rospack
Architecture: source
Version: 2.6.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 
<[email protected]>
Changed-By: Timo Röhling <[email protected]>
Closes: 1127270
Changes:
 ros-rospack (2.6.4-2) unstable; urgency=medium
 .
   * Migrate debian/watch to version 5 format
   * Bump Standards-Version to 4.7.3
   * Fix FTBFS with Boost 1.90 (Closes: #1127270)
Checksums-Sha1:
 cbcb54ad85a4add2fd27a3e4ae08b53d96034ba4 2450 ros-rospack_2.6.4-2.dsc
 0b9188d8d2e976ead156b0535ad061fcb06f7267 6220 ros-rospack_2.6.4-2.debian.tar.xz
Checksums-Sha256:
 98702181ddfeee14d35a530675cbe82e78899a836c3c5704ed5a777b89f3e917 2450 
ros-rospack_2.6.4-2.dsc
 db2de7d4a44b7ca57a86651c773b12bf332de1409288e75a85ff87af5a6660f7 6220 
ros-rospack_2.6.4-2.debian.tar.xz
Files:
 e7dec69118c2adc726d6f72296c0da19 2450 libs optional ros-rospack_2.6.4-2.dsc
 6c9d04f49100ff213b0e6bd665436c83 6220 libs optional 
ros-rospack_2.6.4-2.debian.tar.xz

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

iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmmwf6sACgkQzIxr3RQD
9MpBiQ//REZpt1c0jKoCSZ8+9+uh8Jh7UVw6OPNA8kzXA7TskB2AhSRyfpV+mST7
eGVIJtWZlUdh8rjm4H/N4K31oc2/tkbujKvOzY9ct4oafeAblvVvdSH2BAN7jtkZ
rj8rZI3Z+AuSbnY7cFKJedDtiGutsr9L02sGFMBfZhZk8yWOgUBMTMrpuGRG7bWM
d4BV9Z3fWFHWa0zN6ApSo+cbp0GyVik2/4wT5b9zl0AwQg0F11172Ifsqw/EB/Zk
WGYS2oIJONh7Q6Qaim/v5wi2cy50CEk8RopuSgrbPWkHXfOkZiLHSBWRfbmaZXAo
z7gV8QRe/GoBeJeGMmDMEY6HSc3iKHfGzYbOepLHFnkoip1b5rvUB5z/Nbne7Q+j
LcE8UtwXPi3qHktXPHoU6PKfZwTQjFj57lJpkbzmBD/d/kJu319CQaWJAvq1yMEs
aijD21gVgbfxWxJ0L62uNhJnVqolizYfWffBqdssLoZgj5RmeFRp1Gtk6vtsu1iK
vY4SN8AZdhAKpZYLvANmHHebMFSVmKwSHgZ5mZ2VRK9gI2L+RmsHCsKAthRMl45q
Y+WYmepIR2uRC2Oh2Jico7GsiMiFtb8/P7Slzz/a1VnYT1gbLo4HHNcoh1+JU0T5
09DLHLqmQY4YBu56Dr3yXeSJv5111NlD3pRPCfs1DPErWFBSJYQ=
=Tx4b
-----END PGP SIGNATURE-----

Attachment: pgpQLBesHLIWR.pgp
Description: PGP signature


--- End Message ---

Reply via email to