Bug#1129773: [Debian-med-packaging] Bug#1129773: insighttoolkit5: FTBFS: Could NOT find Boost: Found unsuitable version "1.90.0"

[Steven Robbins]

On Monday, March 9, 2026 9:23:05 a.m. Central Daylight Time Santiago Vila 
wrote:
> On Mon, Mar 09, 2026 at 08:34:26AM -0500, Steven Robbins wrote:
> > I just did a local re-build of vtk9 and indeed the file now contains
> > 
> >  find_package(Boost
> >  
> >    1.90.0
> >    EXACT
> > 
> > Which confirms your hypothesis.
> > 
> > > Therefore, I suggest a rebuild of the vtk package with the new version
> > > of boost, this should update the VTK-vtk-module-find-packages.cmake and
> > > then all the package that depends on vtk9 may rebuild without any
> > > problem.
> > 
> > I agree.  This feels like a binary NMU rebuild would suffice, so I'll make
> > that request.
> Before you request a binNMU, I have a simple question:
> 
> Should we really use EXACT there?

This is a question for the VTK upstream, I'd guess.

In my opinion, the answer is "yes".  I think what is going on is that VTK is  
building its libraries incorporating code from Boost x.y.z.  If a downstream 
code builds on VTK, then it should use the same version of Boost to avoid 
nasty surprises.  Boost does not provide any ABI stability guarantees.

Regards,
-Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20260309/24c13fdb/attachment-0003.sig>