Hi,
Note that this is kind of a duplicate of [0]. I have marked [0] as blocking
this one.
Some further information:
I tried to follow this up a bit. Looking at the upstream expat bugs [1] [2]
it might very well be that vtk9 was relying in internals of expat's xml
processing and their assumptions broke when moving to 2.6.0.
Hence this probably is an incompatibility on vtk9's side rather than a bug in
expat. At least upstream thinks that way in in [1] and closed the bug.
The stalled discussion about this in VTK9 can be found in [3].
Should we reassing this to vtk9?
Best,
Markus
[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064762
[1] https://github.com/libexpat/libexpat/issues/857
[2] https://github.com/libexpat/libexpat/issues/840
[3] https://gitlab.kitware.com/vtk/vtk/-/issues/19258
