[Debian-med-packaging] Bug#764029: Moving GDCMConfig.cmake to new directory broke GDCM_INCLUDE_DIRS and thus builds of dependent code; e.g. ITK

[Steve M. Robbins]

Package: libgdcm2-dev
Version: 2.4.4-2
Severity: important

In 2.4.4-1, the file GDCMConfig.cmake was in /usr/lib/gdcm-2.4, so this code:

  get_filename_component(GDCM_INCLUDE_ROOT "${SELF_DIR}/../../../include/gdcm-2.4" ABSOLUTE)
  set(GDCM_INCLUDE_DIRS ${GDCM_INCLUDE_ROOT})

worked and GDCM_INCLUDE_DIRS was set to /usr/include/gdcm-2.4.

Now the file is one level deeper (/usr/lib/x86_64-linux-gnu) and
GDCM_INCLUDE_DIRS get set to nonsense.

I think GDCM_LIBRARY_DIRS has the same problem.



-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libgdcm2-dev depends on:
ii  libgdcm2.4  2.4.4-2

libgdcm2-dev recommends no packages.

libgdcm2-dev suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/lib/x86_64-linux-gnu/gdcm-2.4/GDCMConfig.cmake (from libgdcm2-dev package)