Your message dated Fri, 20 Mar 2026 09:04:27 +0000
with message-id <[email protected]>
and subject line Bug#1128111: fixed in barada-pam 0.5.3-1.1
has caused the Debian Bug report #1128111,
regarding barada-pam: FTBFS with boost 1.90
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.)
--
1128111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1128111
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:barada-pam
Version: 0.5.3-1
Severity: important
Tags: sid forky ftbfs
User: [email protected]
Usertags: boost1.90
barada-pam FTBFS with boost 1.90. Note that the FTBFS may not necessarily be
connected to boost - please check the build log for the actual cause.
Ubuntu has started the rebuild and the status can be tracked here:
https://transitions.ubuntu.com/html/boost1.90.html#!good,bad,partial,unknown,!notintesting
Thanks to them. Please find your package there, after that you can see the logs
from
the failing build.
Note: This ticket severity will be increased to RC bug when
boost-defaults is switched to 1.90.
Additional information: The boost system library was removed upstream in 1.89
and is empty since 1.69.
If your package depends on or build-depends on libboost-system-dev, remove it
from
build-depends and the build system. See https://www.boost.org/releases/1.89.0/
for cmake instructions.
Note that libboost-system-dev is "virtually" provided by libboost-dev_1.90,
but it is better to drop it from build-depends as this will be removed in the
future.
Here is the most probably relevant part of the failing build log:
quasi_newton.o quaternion.o random.o utils.o vina.o -l boost_system -l
boost_thread -l boost_filesystem -l boost_program_options
/usr/bin/x86_64-linux-gnu-ld.bfd: cannot find -lboost_system: No such file or
directory
collect2: error: ld returned 1 exit status
Thanks,
Anton
--- End Message ---
--- Begin Message ---
Source: barada-pam
Source-Version: 0.5.3-1.1
Done: Adrian Bunk <[email protected]>
We believe that the bug you reported is fixed in the latest version of
barada-pam, 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 barada-pam 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, 18 Mar 2026 18:45:07 +0200
Source: barada-pam
Architecture: source
Version: 0.5.3-1.1
Distribution: unstable
Urgency: medium
Maintainer: Andrew Pollock <[email protected]>
Changed-By: Adrian Bunk <[email protected]>
Closes: 1128111
Changes:
barada-pam (0.5.3-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Remove unnecessary linking with libboost_system. (Closes: #1128111)
Checksums-Sha1:
6081b8a1145ae8209476571e94afce2ceca5b684 1935 barada-pam_0.5.3-1.1.dsc
00e7ac58a1678af74127dc172ce3c542aa47a8a4 5172
barada-pam_0.5.3-1.1.debian.tar.xz
Checksums-Sha256:
531951e246028a12d824b9e6a128b9a962104bc67b944bfd76cf575e252860e8 1935
barada-pam_0.5.3-1.1.dsc
04de031ea83886b6a3ded835b7f7e673e02ba2966b5e7e3bea73e725ca636e41 5172
barada-pam_0.5.3-1.1.debian.tar.xz
Files:
1e38cfe5e34855447d1d96d337f0a299 1935 admin optional barada-pam_0.5.3-1.1.dsc
55e09ee98aeb98ba63e961aeadc70ff0 5172 admin optional
barada-pam_0.5.3-1.1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmm62AkACgkQiNJCh6LY
mLEpJBAAv57o5ebEJX89FCW6MiEL2F9mObN3iKRtw3ABQjx7amK/ptUYIxrFN2eK
mK6Y611y86CIL8XtolJlflGY1z+3LqsP4PlYMIY3FWy2ov+7E154Gp221FCYU/PB
/LNOOfiQXSRwDZueAcpiM0CDu7Wo3eDky4H1tAz9Ktmm/kJc3WYBK1LHaMBD4bqb
Ai4aaTl1v3gyG0+BL0pnYxQKx1z7a4/MqjmQ+pMlAmOysDt6KL6G24Zhq5v8ZxiZ
15eOWSkR7feEJW4bTe23v0Ny6fj7iX7qoyEbD5WXWPmHJrv6b1j/N1C7qnUWELsq
JtfBcVFdGLMaSlMyXxOuMZsgIer9tJ0ilMUuiUBbWnam+FeFc41QvqU39jpACET9
cwWQJWryZ3/u8n2G3IkM50V6K4R5ArERLlClGIZ0oy2GEl7llzCv3QA0/wmdyYeF
Ztf5aeYEH34GaLjtiKHCrewMx8i/sixcnpqva/RMAATL8N2uL40LonXSEHOCCF7G
8pPkjS9yq+wwLKERz90veQVk0RsWzXmREJeTRh8v9c1W/5PNAYUVQIw8q/fCUW9l
vniSR4eDFFmp0Xau+I1jHnL5a9SUgmh0jODa+BlSCEblgmyM2A7ZD2H7y037hgmE
tjY7E29IX/KO9Z4YnQQk8ICOAWuKYXbWs0dQ4PmjJjnp6SzPcTc=
=Rv1e
-----END PGP SIGNATURE-----
pgpcu5YWZa1sN.pgp
Description: PGP signature
--- End Message ---
