Hi, I have found the reason and prepared a fix. vtk9 has not direct dependency on boost, but it is transitive.
I am uploading it with the explicit versioning. BinNMU can resolve it but I want to have a reliable fix. Regards Anton Am Mo., 9. März 2026 um 18:40 Uhr schrieb Steven Robbins <[email protected]>: > > On Monday, March 9, 2026 11:13:09 a.m. Central Daylight Time Sebastian > Ramacher wrote: > > > Control: tags -1 moreinfo > > > > > > Hi Steve > > > > > > On 2026-03-09 08:43:22 -0500, Steve M. Robbins wrote: > > > > Package: release.debian.org > > > > Severity: normal > > > > X-Debbugs-Cc: [email protected] > > > > Control: affects -1 + src:vtk9 > > > > User: [email protected] > > > > Usertags: binnmu > > > > > > > > nmu vtk9_9.5.2+dfsg4-1 . ANY . unstable . -m "Rebuild to capture updated > > > > Boost library default version. At build time, vtk captures the version > > > > of Boost libraries used in its build and generates a cmake file used in > > > > downstream builds that looks for that precise version of boost. The > > > > boost defaults have recently changed - which makes downstream builds fail > > > > (e.g. ITK, Elastix, ANTS). A re-built VTK will pick up the latest boost > > > > default." > > > > > > I am unable to find these boost dependencies in the -dev packages of > > > vtk9. > > > You're right. In fact, I don't even see build-depends on boost packages. > That seems strange to me. I've cc'd the active maintainers: should there be > a build-depends on boost packages? > > > -Steve > > > > If there is such a tight requirement on the installed boost > > > version, why doesn't it have dependencies on the boost version it was > > > built with? > >
