Your message dated Mon, 10 Mar 2014 12:07:51 +0100
with message-id
<ca+7wusxmkk9v96gvhkv4oj86b+5+moptk7t8urgq10hijbd...@mail.gmail.com>
and subject line
has caused the Debian Bug report #735523,
regarding dcap and dicom3tools: error when trying to install together
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
735523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735523
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dicom3tools,dcap
Version: dicom3tools/1.00~20140105-1
Version: dcap/2.47.8-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Date: 2014-01-16
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:
Selecting previously unselected package libjpeg8:amd64.
(Reading database ... 10913 files and directories currently installed.)
Preparing to unpack .../libjpeg8_8d-2_amd64.deb ...
Unpacking libjpeg8:amd64 (8d-2) ...
Selecting previously unselected package libpng12-0:amd64.
Preparing to unpack .../libpng12-0_1.2.49-5_amd64.deb ...
Unpacking libpng12-0:amd64 (1.2.49-5) ...
Selecting previously unselected package libjbig0:amd64.
Preparing to unpack .../libjbig0_2.0-2_amd64.deb ...
Unpacking libjbig0:amd64 (2.0-2) ...
Selecting previously unselected package libtiff5:amd64.
Preparing to unpack .../libtiff5_4.0.3-7_amd64.deb ...
Unpacking libtiff5:amd64 (4.0.3-7) ...
Selecting previously unselected package libdcap1.
Preparing to unpack .../libdcap1_2.47.8-2_amd64.deb ...
Unpacking libdcap1 (2.47.8-2) ...
Selecting previously unselected package dcap.
Preparing to unpack .../dcap_2.47.8-2_amd64.deb ...
Unpacking dcap (2.47.8-2) ...
Selecting previously unselected package libnetpbm10.
Preparing to unpack .../libnetpbm10_2%3a10.0-15+b2_amd64.deb ...
Unpacking libnetpbm10 (2:10.0-15+b2) ...
Selecting previously unselected package netpbm.
Preparing to unpack .../netpbm_2%3a10.0-15+b2_amd64.deb ...
Unpacking netpbm (2:10.0-15+b2) ...
Selecting previously unselected package dicom3tools.
Preparing to unpack .../dicom3tools_1.00~20140105-1_amd64.deb ...
Unpacking dicom3tools (1.00~20140105-1) ...
dpkg: error processing archive
/var/cache/apt/archives/dicom3tools_1.00~20140105-1_amd64.deb (--unpack):
trying to overwrite '/usr/share/man/man1/dccp.1.gz', which is also in package
dcap 2.47.8-2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for man-db (2.6.5-3) ...
Errors were encountered while processing:
/var/cache/apt/archives/dicom3tools_1.00~20140105-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
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/bin/dccp
/usr/share/man/man1/dccp.1.gz
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/.
--- End Message ---
--- Begin Message ---
Control: fixed -1 1.00~20140306-1
--- End Message ---
