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

Johannes Schauer Marin Rodrigues josch at debian.org
Tue May 3 21:17:24 BST 2022


Source: dcmtk
Version: 3.6.6-5
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: tille at debian.org

Hi Andreas,

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.

Thanks!

cheers, josch



More information about the Debian-med-packaging mailing list