[Debian-med-packaging] Bug#1010536: libdcmimage.so.16: cannot open shared object file: No such file or directory

[Johannes Schauer Marin Rodrigues]

Hi,

On Tue, 03 May 2022 22:17:24 +0200 Johannes Schauer Marin Rodrigues <josch at debian.org> wrote:
> thanks for your upload of the new upstream version of dcmtk.  Unfortunately,
> I think this is missing a proper transition because the ABI and thus the
> SONAME changed. This can also be seen in the autopkgtests of biosig, odil and
> odin which all fail with a similar error right now:
> 
> biosig & odil: ImportError: libdcmdata.so.16: cannot open shared object file: No such file or directory
> 
> odin: gencoil: error while loading shared libraries: libdcmimgle.so.16: cannot open shared object file: No such file or directory
> 
> This is because the new upstream version bumped the SONAME from 16 to
> 17. This means, that the binary package name should also change from
> libdcmtk16 to libdcmtk17. This probably would've been caught by
> lintian if package-name-doesnt-match-sonames wasn't overridden in
> debian/libdcmtk16.lintian-overrides... :/
> 
> The package should've probably first been uploaded to experimental,
> would go through binary-NEW and create a auto-dcmtk transition. I'm
> unsure how to clean this up now that the package has already been
> uploaded to unstable.
> 
> I'm going to rebuild all reverse dependencies and see if anything breaks
> and report back to you in case I find any FTBFS caused by the new dcmtk
> version.

the following source package build depend on libdcmtk-dev:

aeskulap, amide, ants, biosig, cmtk, dicomscope, elastix, insighttoolkit4,
insighttoolkit5, itksnap, mia, odil, odin, openimageio, orthanc, orthanc-wsi,
plastimatch

I cannot test insighttoolkit4 or insighttoolkit5 because my system lacks the
resources to successfully build either source package (No space left on
device).

ants FTBFS but is broken beyond repair and hasn't been in testing since 2017.

itksnap FTBFS for for an unrelated reason (#1010549).

plastimatch FTBFS because of a missing build dependency on
libinsighttoolkit5-dev: https://buildd.debian.org/status/package.php?p=plastimatch

It seems the new dcmtk version did not just bump ABI but also changed its API
(the DcmTransportLayerStatus enum including TCS_ok was removed from dcmlayer.h
and defining INCLUDE_{CSTRING,CSTDLIB,CSTDIO} now raises an error), so some
patches were necessary:

biosig: #1010545
orthanc: #1010554

Mathieu, since you filed #1010474 (upgrading dcmtk to 3.6.7) could you help
clean this up? For example maybe you find a solution to get orthanc to
successfully compile again (I X-Debbugs-Cc-ed you on the last bug). Currently,
the testsuite fails with:

/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libdcmdata.so: undefined reference to symbol 'inflateEnd'
/usr/bin/ld: /lib/x86_64-linux-gnu/libz.so.1: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status

Which may be something that we have to fix in dcmtk?

Note, that I'm not a Debian Med team member. I'm just putting my time here,
because the last dcmtk upload broke blender (because it depends on openimageio)
which in turn hampers my work on the MNT Reform system image. So for me this is
just one big yak shave...

Thanks!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/debian-med-packaging/attachments/20220504/92c13ac9/attachment-0001.sig>