Your message dated Mon, 30 Mar 2026 05:18:33 +0000
with message-id <[email protected]>
and subject line Bug#1128162: fixed in slic3r-prusa 2.9.4+dfsg-4
has caused the Debian Bug report #1128162,
regarding slic3r-prusa: 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.)


-- 
1128162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1128162
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:slic3r-prusa
Version: 2.9.4+dfsg-3
Severity: important
Tags: sid forky ftbfs
User: [email protected]
Usertags: boost1.90

Dear Maintainer,

slic3r-prusa 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:




This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Error at 
/usr/lib/x86_64-linux-gnu/cmake/Boost-1.90.0/BoostConfig.cmake:141 
(find_package):
  Could not find a package configuration file provided by "boost_system"
  (requested version 1.90.0) with any of the following names:

    boost_systemConfig.cmake
    boost_system-config.cmake

  Add the installation prefix of "boost_system" to CMAKE_PREFIX_PATH or set
  "boost_system_DIR" to a directory containing one of the above files.  If
  "boost_system" provides a separate development package or SDK, be sure it
  has been installed.
Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/Boost-1.90.0/BoostConfig.cmake:262 
(boost_find_component)
  /usr/share/cmake-3.31/Modules/FindBoost.cmake:610 (find_package)
  CMakeLists.txt:377 (find_package)


-- Configuring incomplete, errors occurred!
cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt


Thanks,

Anton

--- End Message ---
--- Begin Message ---
Source: slic3r-prusa
Source-Version: 2.9.4+dfsg-4
Done: Chow Loong Jin <[email protected]>

We believe that the bug you reported is fixed in the latest version of
slic3r-prusa, 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.
Chow Loong Jin <[email protected]> (supplier of updated slic3r-prusa 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: Sun, 29 Mar 2026 19:05:52 +0800
Source: slic3r-prusa
Built-For-Profiles: noudeb
Architecture: source
Version: 2.9.4+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian 3-D Printing Packages 
<[email protected]>
Changed-By: Chow Loong Jin <[email protected]>
Closes: 1128162
Changes:
 slic3r-prusa (2.9.4+dfsg-4) unstable; urgency=medium
 .
   * [587ca15] Fix FTBFS with boost 1.90 (Closes: #1128162)
Checksums-Sha1:
 ce1ea6b2f17b12241b4543e9429bf5b5fb6924ec 2837 slic3r-prusa_2.9.4+dfsg-4.dsc
 7298ede3b83c56c9021345c36cdbe1385453aaff 60544 
slic3r-prusa_2.9.4+dfsg-4.debian.tar.xz
 7789372a76cc46c17d8412b712b3ea135d2be286 17207 
slic3r-prusa_2.9.4+dfsg-4_source.buildinfo
Checksums-Sha256:
 6e110be402e9dbf9f70461efab0555840d8b018e9e630798f0c177bc72537c31 2837 
slic3r-prusa_2.9.4+dfsg-4.dsc
 00e8bc4f7e80a94a1f49f2ccc541955cb1b3570dd831cfdc3df6c3412159ffad 60544 
slic3r-prusa_2.9.4+dfsg-4.debian.tar.xz
 288bb48ded3b59e71f2ff8f8022741701763cbc725a0145d58e9cb57b4428e92 17207 
slic3r-prusa_2.9.4+dfsg-4_source.buildinfo
Files:
 10c92baf63e0c30518e245c9fd12f438 2837 misc optional 
slic3r-prusa_2.9.4+dfsg-4.dsc
 930d4f584ccae1e81e653f51102dcc35 60544 misc optional 
slic3r-prusa_2.9.4+dfsg-4.debian.tar.xz
 0995184146a85055563b01273fe100fe 17207 misc optional 
slic3r-prusa_2.9.4+dfsg-4_source.buildinfo

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

iQIzBAEBCgAdFiEEEuDQnfs/9/dZ027Q+9UiW1iHUqEFAmnKA2AACgkQ+9UiW1iH
UqHrjw/9F8ZGgo73IJJZQgIgKa1o2gIFoYh21nof4eE7XG8rySklxFRVV885n/dg
ykM5moKiMW/i71I9x3JgYn+QxbhgSu6o1alPZ1mfRdZSGMApEwF0aNMb22VwtKw6
g9+NfK8VOyRlmRwqRVd57V54gfQV62En0KEmudpIhGhvVarAozloZ+I9m4Ef6i/z
nCYsnEF5vRXMnt00YbUMLIhYUXIX1/7RSjimla+a94bKGw/qPqh3UY2Qr9b5Mhdo
v9vxQrMQkLML5ULUaXF4sj7eMA1Wq5mFYofHYCSsESIA3gtXJle6wBqJY65nRvd4
n54o8tauIeXUx/9CnpLKjvkcEZwAg7JNKxaeK52d14djbhyg86vTZ2rmwigasYkp
8RkG6IbtL6UtCTXjNJ+TU/Rj/zBQ6Z10YMaxQEcLgE1wHkCNhsm+37RUrh59blmV
fTpaeS7B89qE16+I5oFK7RVGsH8l/x/QUp/HF7c6d5LraXlo6zAW94Pbe9CdYUdO
UO53cc4rZKiEcuQNs49xe8rywiY6CY3Gsy51oDQco+aZI2Xmqj2URpq7EEyJreQd
YJyP8r7TyQQ5PGtziMCuHDxKPQzyNqkfJOSYO70Cei/Kzwv8WfdkC1aLDVWW64wg
MXHGIO5oG+APaINoq0b+3al7YB5BkQokk696wo5IAIBKCqQvxQo=
=zqEJ
-----END PGP SIGNATURE-----

Attachment: pgpOtiEq0HxyC.pgp
Description: PGP signature


--- End Message ---

Reply via email to