Your message dated Mon, 09 Mar 2026 18:05:13 +0000
with message-id <[email protected]>
and subject line Bug#1127610: fixed in esys-particle 2.3.5+dfsg2-13
has caused the Debian Bug report #1127610,
regarding esys-particle: 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.)
--
1127610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127610
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:esys-particle
Version: 2.3.5+dfsg2-12
Severity: important
Tags: sid forky ftbfs
User: [email protected]
Usertags: boost1.90
Dear Maintainer,
esys-particle 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:
configure:5249: $? = 1
configure:5269: checking whether the C compiler works
configure:5291: mpicc -Wall -g -O2 -Werror=implicit-function-declaration
-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -flto=auto -ffat-lto-objects
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -fcf-protection
-fdebug-prefix-map=/<<PKGBUILDDIR>>=/usr/src/esys-particle-2.3.5+dfsg2-12build1
-Wdate-time -D_FORTIFY_SOURCE=3 -lboost_system -Wl,-Bsymbolic-functions
-Wl,--package-metadata=%7B%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22esys-particle%22%2C%22version%22:%222.3.5+dfsg2-12build1%22%2C%22architecture%22:%22amd64%22%7D
-flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now
-Wl,-rpath,/usr/lib/python3/dist-packages/esys/lsm/util:/usr/lib/python3/dist-packages/esys/lsm
conftest.c >&5
/usr/bin/x86_64-linux-gnu-ld.bfd: cannot find -lboost_system: No such file or
directory
Thanks,
Anton
--- End Message ---
--- Begin Message ---
Source: esys-particle
Source-Version: 2.3.5+dfsg2-13
Done: Anton Gladky <[email protected]>
We believe that the bug you reported is fixed in the latest version of
esys-particle, 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.
Anton Gladky <[email protected]> (supplier of updated esys-particle 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: Mon, 09 Mar 2026 18:28:22 +0100
Source: esys-particle
Architecture: source
Version: 2.3.5+dfsg2-13
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
<[email protected]>
Changed-By: Anton Gladky <[email protected]>
Closes: 1127610 1128156
Changes:
esys-particle (2.3.5+dfsg2-13) unstable; urgency=medium
.
* [31bc51c] update copyright and add lrc.config
* [82a3a79] chore(salsa-ci): enable lintian and licenserecon
* [98acf13] Drop boost system (Closes: #1128156, #1127610)
* [172d3a3] chore(salsa-ci): disable debrebuild job
* [cde5f38] chore(debian): replace libboost-all-dev with specific libs
Checksums-Sha1:
94cb2264e2e58dbac93b409909b256d18ff3918e 2650 esys-particle_2.3.5+dfsg2-13.dsc
862c4c28da570300d84793b34c88ce5eb0641e0f 578536
esys-particle_2.3.5+dfsg2-13.debian.tar.xz
585d13d27c29b8ad880ecb78742547ae3a5c3ac5 5658760
esys-particle_2.3.5+dfsg2-13.git.tar.xz
b81aa070ddf6f894645dec3af0d41e4c52fcd866 17348
esys-particle_2.3.5+dfsg2-13_source.buildinfo
Checksums-Sha256:
0fc1bbcb61e8b3556c302e33ffe18844b6f2d751fbcf41cbef64a8580fc03d44 2650
esys-particle_2.3.5+dfsg2-13.dsc
f456e5a38926b1fc5a51f8181b6a95293b8368f972d7b05cb6f41a8ba1d841d1 578536
esys-particle_2.3.5+dfsg2-13.debian.tar.xz
7d768ce1fcbaad844867886949614e8cf45b3cc7a4b18b9dd3fcc27656479fcc 5658760
esys-particle_2.3.5+dfsg2-13.git.tar.xz
4486c7ba4789839c0fde44b3db4ed43737f96cd26ed8d93a839eb5d324e55b0c 17348
esys-particle_2.3.5+dfsg2-13_source.buildinfo
Files:
98d58e17b70450b870eedb6f7cdcc852 2650 science optional
esys-particle_2.3.5+dfsg2-13.dsc
a1b6979d630e009fec71e4bb8478e473 578536 science optional
esys-particle_2.3.5+dfsg2-13.debian.tar.xz
ca4f8bc271f1ac9fac987762d41a4638 5658760 science optional
esys-particle_2.3.5+dfsg2-13.git.tar.xz
4dfd8cd748740b6976d4ef9331e25f9a 17348 science optional
esys-particle_2.3.5+dfsg2-13_source.buildinfo
Git-Tag-Info: tag=f04c90689a3f8ef570d9c4a277f88655622f5144
fp=bbbd45ea818ab86ff67e7285d3e17383cfa7ff06
Git-Tag-Tagger: Anton Gladky <[email protected]>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmmvBVwACgkQYG0ITkaD
wHmNPA//arTaz/bXND8GeqPV8wL7gaSris4Oas65UmvoJlliuYcoixNNkSbhhhN4
z5gD52ppyrZAjT7s4BZ7W5fvayfTGMxCq59Y8pYP0IokGLTWeiFwXz2AZy2FLX+G
O1hNTj4mZInw5+TXYOjSMKTb2HEXmBlUXqNG9bbNSPtgfAmG2S/sLj2DCVU+76rU
zKf1MbVAnxjdajfBYcU/Xk1BYCa7ZZAP+mMYzJziO6bafCNX0vgsGY8w7nC4P/PA
SsslhQS6amizLmfysCu61Fs1ztcaBYJBfRKRGWZLx1bTNE8ipnfJToRkP8YR2evz
3HA9Xok5IZOL11TvNqHouhn2iSGaJgv/L0NYUHbwxR8a7+jGdIQFtFz1UN6dT4Ih
csFZDRBHoQbXcugKXCbByi26Qzb3N8milMfWHXgzx4yj1GqbqUWmekkBML7HI9Qn
/hVd2dMGqdzwo1fwqczNmYULw28CJApQlhz0eY8QbqTaoJoe897JzYEj22wn/2Q5
Q1DufnkjFl+JkbdZW9vUOaC4oPxlQuEf1Iy1OPr4q2LDKOy4GcWW683cm74qubXi
vTSDyn2WBNSvjrijGPKrZ0vHkgopCtBw4zZjld/5Tzkqvo08czsbvV4xrBCRChZI
S+bNhW+1s31FB+zu5BNhKi95MwQLt1eRJAjpdAjidQ7VGuBVoy0=
=r5tM
-----END PGP SIGNATURE-----
pgpCCEYnb2Mc1.pgp
Description: PGP signature
--- End Message ---
