Your message dated Wed, 11 Mar 2026 17:33:53 +0000
with message-id <[email protected]>
and subject line Bug#1127271: fixed in ros-ros-comm 1.17.4+ds-4
has caused the Debian Bug report #1127271,
regarding ros-ros-comm: 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.)
--
1127271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127271
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:ros-ros-comm
Version: 1.17.4+ds-3
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-ros-comm
Source-Version: 1.17.4+ds-4
Done: Timo Röhling <[email protected]>
We believe that the bug you reported is fixed in the latest version of
ros-ros-comm, 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-ros-comm 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: Wed, 11 Mar 2026 17:58:17 +0100
Source: ros-ros-comm
Architecture: source
Version: 1.17.4+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
<[email protected]>
Changed-By: Timo Röhling <[email protected]>
Closes: 1127271
Changes:
ros-ros-comm (1.17.4+ds-4) unstable; urgency=medium
.
* Bump Standards-Version to 4.7.3
* Fix FTBFS with Boost 1.90 (Closes: #1127271)
Checksums-Sha1:
3b5f29661df392e46022a9c00813dff0842f2d71 5548 ros-ros-comm_1.17.4+ds-4.dsc
cc1a374672cfe60e29d50bea4e6b00cf98c76c18 19360
ros-ros-comm_1.17.4+ds-4.debian.tar.xz
Checksums-Sha256:
1c8b4816258bcc3f991b5b4ff2a48fea2c7d4b11a783f7a2bd015b1f3e74c03d 5548
ros-ros-comm_1.17.4+ds-4.dsc
dcfb874ea6c37ba581afbb131a0d9300db32f3f47e496d5b891785c349a157b6 19360
ros-ros-comm_1.17.4+ds-4.debian.tar.xz
Files:
6463b5fdccf7f9e866de6722ed7952ca 5548 libs optional
ros-ros-comm_1.17.4+ds-4.dsc
27b2d8100bacb21cd73dfa69774c52f7 19360 libs optional
ros-ros-comm_1.17.4+ds-4.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmmxpHwACgkQzIxr3RQD
9MpPKhAAnpDglh7eTdBtrPvflg0kF8Q8BhPxrss/L72snjjjra7INkwQf23iGlRQ
UCEozkWdYC0S0ZrJ9MwLicDZANXIPUTMZAGNkFcMSDS9DYWF0R6dFv2WVAX0ZFdq
mMBnKUw2G0wBk3AmecneQHc6r1U8+IDAOlGHmHKM6a5s10F3ovyrSObLfxVqcaMy
QLnJI7o+tM/i2mMaO8tEkLVFp/dowmr0X3jJobltDdTXvdoVQ3dtlh3Xt49IGHav
zVvdS2+9UALCafwdiOJvWXknEkYEsI6fHWupc27z17iOai/wbFFITco6NaDI0Iwq
jt8atYJG8oLz7TR5mt7q3Vd70uM52sXOIOL3TrLmD92RPnKGh1lvLE2gl6Yc9U9V
wlDvmx5R7lGqL1hKVem4QHT+RbDcAbyXKO3khjK/9zA3doI5AmWBWDRMVvoRPwZt
CoschMAoregCLdGE23Uroc9s/d+YH08Is3/oUWwAOUZmCDhBx41eqtWVWH3960xR
pR3cQz8KFoVTQf3WQTlcpOMKA81pXB747Ec0QJRMJbRCEg4yWovFFEuG0LdnZHWW
gR+RI6GZNHUlqHhBkX1L6HXWH6CXeu6W6I5eBfjLwmEGRADwDabv4GXeYRCCQP0I
ZpLTgGIh3k48uVqyzHSjhiRtFy23Tmpm+PVQmaSf3Og2lFEDktU=
=H6is
-----END PGP SIGNATURE-----
pgpqpHdk9yvVR.pgp
Description: PGP signature
--- End Message ---
