[Debian-med-packaging] Bug#911793: Bug#911793: autopkgtest regression: Segmentation fault

[Emmanuel Promayon]

Dear Paul,

On 19/11/2018 19:32, Paul Gevers wrote:
>
>> It seems camitk-4.1.2-2 is not very lucky!
> So you are caught in the hdf5 transition:
> https://release.debian.org/transitions/html/auto-hdf5.html
Yes, you are right.

>> The current deadline for camitk package removal is 22 November.
>>
>> What do you think is the best course of action?
> If you comment on the RC bug that is triggering the autoremoval, then
> the timer gets reset. Just explain there why it can't be fixed NOW. I
> still agree with Mattia: "This is the signature of an ABI break not
> correctly handled." so I believe that should be fixed first.

The RC bug that triggered the autoremoval is #909120 [1] and (I hope it) 
should be fixed by camitk version 4.1.2-2 (now in unstable and 
struggling to get into testing). The bug was closed automatically by the 
upload ot 4.1.2-2.
Just to make sure that I understand correctly about the autoremoval: if 
I comment on #909120  it should delay the autoremoval?
I understand as well that it might not be the best thing to do first (I 
just like to understand a bit better).

About the ABI break: I am sorry to say that I don't really understand 
how to fix this.
Is it possible that this ABI breaks comes from the fact camitk 4.1.2-1 
is based on vtk6 (which introduced #909120 in the first place when gdcm 
 >= 2.8.7-2 moved from python2 to python3 and consequently from vtk6 to 
vtk7) while camitk-4.1.2-2 is based on vtk7 and gdcm >= 2.8.7-2?
If yes, should I add a "Breaks: vtk6" in d/control of camitk?And/or as 
you suggested earlier should I add "gdcm >= 2.8.8"? Or it is something 
(like "Breaks:vtk6") that should be done in gdcm or vtk7 instead?

Thank you again for your message... and for your patience (and do not 
hesitate to refer me to some documentation or example, my packager 
training is far from being finished, as you can see!)

Best regards,
Emmanuel

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909120