<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 12.09.25 17:58, Santiago Vila wrote:<br>
</div>
<blockquote type="cite" cite="mid:aMRDOLDV0MlZAIx7@nuc">
<pre wrap="" class="moz-quote-pre">On Fri, Sep 12, 2025 at 04:58:33PM +0200, Markus Blatt wrote:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">This is bug 1064762 that has now probably been added to bookworm by a patch
to vtk9.
I can work around this here by simply deactivating test, but this kind of
reading of the vtk files I cannot fix here. dune-grid just writes those
files.
The underlying problem can only be fixed in VTK. though. It might affect
other packes.
How should we proceed?
</pre>
</blockquote>
<pre wrap="" class="moz-quote-pre">
I think it all depends on much effort we[*] are willing to make.
At this point in the life of bookworm (which is 2/3 of its supported
period), there are already at least 60 different ftbfs bugs, so I
would say that fixing the FTBFS problem alone (disabling the offending
tests, if that's your plan and you know how to do it) would be more
than acceptable and a lot better than nothing.</pre>
</blockquote>
<p>I'll start with that then.<br>
</p>
<p>This will leave the main problem, though:</p>
<p>Due to the security fix in expat [1], you will not be able to
process any binary vtk files in bookworm<br>
(e.g. visualize them in paraview) anymore.</p>
<p>To fix that we would need to backport [2] to vtk9</p>
<p>[1]
<a class="moz-txt-link-freetext" href="https://tracker.debian.org/news/1647706/accepted-expat-250-1deb12u2-source-into-proposed-updates/">https://tracker.debian.org/news/1647706/accepted-expat-250-1deb12u2-source-into-proposed-updates/</a><br>
</p>
<p>[2]<a
href="https://gitlab.kitware.com/vtk/vtk/-/issues/19258#note_1510307"> </a><a class="moz-txt-link-freetext" href="https://gitlab.kitware.com/vtk/vtk/-/commit/db8f9efca220c9d16a30958e179abae3379d0011">https://gitlab.kitware.com/vtk/vtk/-/commit/db8f9efca220c9d16a30958e179abae3379d0011</a></p>
</body>
</html>