[Debian-med-packaging] Bug#658218: libgdcm2.2-dbg and libgdcm2.0-dbg: error when trying to install together

Ralf Treinen treinen at free.fr
Wed Feb 1 06:35:51 UTC 2012


Package: libgdcm2.0-dbg,libgdcm2.2-dbg
Version: libgdcm2.0-dbg/2.0.19-3+b1
Version: libgdcm2.2-dbg/2.2.0-2
Severity: serious
User: treinen at debian.org
Usertags: edos-file-overwrite

Date: 2012-02-01
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


WARNING: The following packages cannot be authenticated!
  libexpat1 libcharls1 libopenjpeg2 libgdcm2.0 libgdcm2.2 libgdcm2.0-dbg
  libgdcm2.2-dbg
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously unselected package libexpat1.
(Reading database ... 10529 files and directories currently installed.)
Unpacking libexpat1 (from .../libexpat1_2.0.1-7.2_amd64.deb) ...
Selecting previously unselected package libcharls1.
Unpacking libcharls1 (from .../libcharls1_1.0-1_amd64.deb) ...
Selecting previously unselected package libopenjpeg2.
Unpacking libopenjpeg2 (from .../libopenjpeg2_1.3+dfsg-4_amd64.deb) ...
Selecting previously unselected package libgdcm2.0.
Unpacking libgdcm2.0 (from .../libgdcm2.0_2.0.19-3+b1_amd64.deb) ...
Selecting previously unselected package libgdcm2.2.
Unpacking libgdcm2.2 (from .../libgdcm2.2_2.2.0-2_amd64.deb) ...
Selecting previously unselected package libgdcm2.0-dbg.
Unpacking libgdcm2.0-dbg (from .../libgdcm2.0-dbg_2.0.19-3+b1_amd64.deb) ...
Selecting previously unselected package libgdcm2.2-dbg.
Unpacking libgdcm2.2-dbg (from .../libgdcm2.2-dbg_2.2.0-2_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/libgdcm2.2-dbg_2.2.0-2_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/debug/usr/bin/gdcmviewer', which is also in package libgdcm2.0-dbg 2.0.19-3+b1
configured to not write apport reports
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libgdcm2.2-dbg_2.2.0-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
cow-shell unlink .ilist: No such file or directory


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/lib/debug/usr/bin/gdcm2vtk
  /usr/lib/debug/usr/bin/gdcmanon
  /usr/lib/debug/usr/bin/gdcmconv
  /usr/lib/debug/usr/bin/gdcmdump
  /usr/lib/debug/usr/bin/gdcmgendir
  /usr/lib/debug/usr/bin/gdcmimg
  /usr/lib/debug/usr/bin/gdcminfo
  /usr/lib/debug/usr/bin/gdcmpdf
  /usr/lib/debug/usr/bin/gdcmraw
  /usr/lib/debug/usr/bin/gdcmscanner
  /usr/lib/debug/usr/bin/gdcmtar
  /usr/lib/debug/usr/bin/gdcmviewer
  /usr/lib/debug/usr/lib/jni/libgdcmjni.so
  /usr/lib/debug/usr/lib/jni/libvtkgdcmJava.so
  /usr/lib/debug/usr/lib/libvtkgdcmPythonD.so
  /usr/lib/debug/usr/lib/python2.7/dist-packages/_gdcmswig.so
  /usr/lib/debug/usr/lib/python2.7/dist-packages/libvtkgdcmPython.so

This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://edos.debian.net/file-overwrites/.





More information about the Debian-med-packaging mailing list