Dear Paul,
Thank you for your investigation.
From the autopkgtest log [1], it seems that vtk6 is installed along
side vtk7.
My understanding of this problem is as follow (I put the debian-med list
in copy so that they can correct me if I am wrong)
- gdcm 2.8.7-1 depends on vtk6
- gdcm 2.8.7-2 moved to python3 and vtk7
- as camitk-4.1.2-1 depends on vtk6 and gdcm, when gdcm 2.8.7-2 went
into unstable, this generated bug #909120, which is a FTBS on unstable
due to the fact that both vtk6 and vtk7 were installed and at run time
the conflict generated a segfault (and I think that the same segfault is
causing #911793)
- gdcm was blocked into unstable because of other issues, and was
updated recently to fix these other issues (mainly python version
conflict and a problem with poppler). gdcm 2.8.7-5 is now in unstable,
and should fix all problems (big thanks to Gert and Gianfranco!)
- I updated to camitk-4.1.2-2 so that it only depends on vtk7. vtk6
should not be installed by autopkgtest (and is not when run inside
unstable).
IMHO is that this autopkgtest regression is due to the fact that testing
has gdcm 2.8.7-1 (that depends on vtk6), while unstable has gdcm 2.8.7-5
(uploaded 22 october, that depends on vtk7 only).
This problem should go away when gdcm 2.8.7-5 enters testing.
Let me know what you think of this analysis and what I can do to help (I
just have a partial understanding on how these kind of problems should
be solved/displayed).
Best regards,
Emmanuel
[1]
https://ci.debian.net/data/autopkgtest/testing/amd64/c/camitk/1201581/log.gz
