[Debian-med-packaging] Fail to build SimpleITK with ITK v4.12

[Ghislain Vaillant]

On 12/08/17 16:25, Gert Wollny wrote:
> Am Samstag, den 12.08.2017, 10:51 +0100 schrieb Ghislain Vaillant:
>> Dear all,
>>
>> Since the update to ITK version 4.12 which recently landed in
>> unstable, SimpleITK fails to build from source. The build log reports
>> a failure to find the gdcm headers used by ITK. The error from the
>> latest build on debomatic is pasted below:
> 
>> I am also concerned by the following detail: gdcm was recently bumped
>> to the 2.8.x series, but the include directory is still
>> `/usr/include/gdcm-2.6` according to the above build log. That
>> sounds wrong to me.
> 
> I did the upload of gdcm-2.8 and itk-4.12 to unstable on the same day,
> and  for that reason the package ITK-4.12 was still build against gdcm-
> 2.6. Unfortunately, this can not be automatically recorded in the
> dependencies of libinsighttoolkit4-dev and I also should have set the
> build-deps to libgdcm2-dev (>=2.8).

So, nothing to be done on my end with SimpleITK.

> To correct the issue a rebuild of ITK is needed, but because of #871677
> respective #871573 this is currently not possible.

:(

> If upstream doesn't solve #871573 in the next few says I will disable
> the python bindings in order to keep the reverse dependencies in
> testing and re-enable them when the bug is fixed, though.

What do we need the Python bindings for?

Ghis