It looks like gdcm recently replaced libgdcm2-dev, libgdcm2.8, libvtkgdcm2-dev 
and libvtkgdcm2.8a with libgdcm2-dev, libgdcm2.8, libvtkgdcm2-dev and 
libvtkgdcm2.8a

The cruft report shows a bunch of stuff (build-)depending on the old packages.
Only insighttoolkit4 seems to have been updated for this change so-far (and 
that still has a bunch of packages depending on it's own old shared library)

* source package gdcm version 3.0.4-1 no longer builds
   binary package(s): libgdcm2-dev libgdcm2.8 libvtkgdcm2-dev libvtkgdcm2.8a
   on amd64,arm64,armel,armhf,i386,mips64el,mipsel,ppc64el,s390x
   - suggested command:
     dak rm -m "[auto-cruft] NBS (no longer built by gdcm)" -s unstable -a 
amd64,arm64,armel,armhf,i386,mips64el,mipsel,ppc64el,s390x -p -R -b libgdcm2-dev 
libgdcm2.8 libvtkgdcm2-dev libvtkgdcm2.8a
   - broken Depends:
     camitk: libcamitk-dev [amd64 i386]
             libcamitk4 [amd64 i386]
     elastix: elastix [amd64 i386]
     fw4spl: fw4spl [amd64 i386]
     insighttoolkit4: libinsighttoolkit4.12 [amd64 i386]
     itksnap: itksnap [amd64 i386]
     nifti2dicom: nifti2dicom [amd64 i386]
                  qnifti2dicom [amd64 i386]
     octave-dicom: octave-dicom
     opencv: libopencv-imgcodecs-dev
             libopencv-imgcodecs3.2
             libopencv-imgcodecs4.1
     orthanc-dicomweb: orthanc-dicomweb
     orthanc-webviewer: orthanc-webviewer
     simpleitk: libsimpleitk1.0 [amd64 i386]
     vtk-dicom: libvtkdicom0.8
   - broken Build-Depends:
     camitk: libgdcm2-dev
             libvtkgdcm2-dev
     fw4spl: libgdcm2-dev
             libvtkgdcm2-dev
     itksnap: libgdcm2-dev
     octave-dicom: libgdcm2-dev
     opencv: libgdcm2-dev
             libvtkgdcm2-dev
     orthanc-dicomweb: libgdcm2-dev
     orthanc-webviewer: libgdcm2-dev
     plastimatch: libgdcm2-dev
     vmtk/non-free: libvtkgdcm2-dev
     vtk-dicom: libgdcm2-dev

Are there plans to deal with fixing this centrally, or should I go ahead and 
file bugs against all the reverse dependencies (I already filed one against 
opencv before I was aware of the scale of this issue)

-- 
debian-science-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Reply via email to