<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body><br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">On Fri, 6 Mar 2026 16:09:33 +0100 Emmanuel Promayon <Emmanuel.Promayon@univ-grenoble-alpes.fr> wrote:</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> Dear Santiago,</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> From what I understand:</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> - VTK-vtk-module-find-packages.cmake is generated during VTK build (by </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> the CMake/vtkModule.cmake script)</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> - It probably catches the Boost version used/detected during build and </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> write it down to VTK-vtk-module-find-packages.cmake</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> - VTK-vtk-module-find-packages.cmake is then exported and used in all </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> projects that depend on VTK (I saw that all them have a new RC error, </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> and they seem to be all the same as the one you found on insighttoolkit)</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> - boost-default has jumped up from 1.83 to 1.90 and landed in unstable </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> on 5 March, VTK 9.52 was last build just before on 3 March.</p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">I just did a local re-build of vtk9 and indeed the file now contains </p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><span style="font-family:monospace;"><span style="background-color:#ffffff;"><span style="color:#000000;"> find_package(</span></span><span style="background-color:#000000;"><span style="color:#ffffff;">Boost</span></span><span style="background-color:#ffffff;"><span style="color:#000000;"> </span></span><br /><span style="background-color:#ffffff;"><span style="color:#000000;"> 1.90.0 </span></span><br /><span style="background-color:#ffffff;"><span style="color:#000000;"> EXACT</span></span><br /><br />Which confirms your hypothesis.</p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> Therefore, I suggest a rebuild of the vtk package with the new version </span></p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> of boost, this should update the VTK-vtk-module-find-packages.cmake and </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> then all the package that depends on vtk9 may rebuild without any problem.</p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">I agree. This feels like a binary NMU rebuild would suffice, so I'll make that request.</p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">-Steve</p>
<br /><br /></body>
</html>