Bug#771647: libphobos-4.9-dev and libphobos-4.8-dev: error when trying to install together
Package: libphobos-4.8-dev,libphobos-4.9-dev
Version: libphobos-4.8-dev/4.8.3-15
Version: libphobos-4.9-dev/4.9.2-4
Severity: serious
User: treinen@debian.org
Usertags: edos-file-overwrite
Date: 2014-12-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:
Selecting previously unselected package gcc-4.9-base:amd64.
(Reading database ... 10910 files and directories currently installed.)
Preparing to unpack .../gcc-4.9-base_4.9.2-4_amd64.deb ...
Unpacking gcc-4.9-base:amd64 (4.9.2-4) ...
Setting up gcc-4.9-base:amd64 (4.9.2-4) ...
(Reading database ... 10917 files and directories currently installed.)
Preparing to unpack .../libgcc1_1%3a4.9.2-4_amd64.deb ...
Unpacking libgcc1:amd64 (1:4.9.2-4) over (1:4.8.2-19) ...
Setting up libgcc1:amd64 (1:4.9.2-4) ...
Processing triggers for libc-bin (2.19-13) ...
(Reading database ... 10917 files and directories currently installed.)
Preparing to unpack .../libstdc++6_4.9.2-4_amd64.deb ...
Unpacking libstdc++6:amd64 (4.9.2-4) over (4.8.2-19) ...
Setting up libstdc++6:amd64 (4.9.2-4) ...
Processing triggers for libc-bin (2.19-13) ...
(Reading database ... 10930 files and directories currently installed.)
Preparing to unpack .../gcc-4.8-base_4.8.3-15_amd64.deb ...
Unpacking gcc-4.8-base:amd64 (4.8.3-15) over (4.8.2-19) ...
Selecting previously unselected package libc-dev-bin.
Preparing to unpack .../libc-dev-bin_2.19-13_amd64.deb ...
Unpacking libc-dev-bin (2.19-13) ...
Selecting previously unselected package linux-libc-dev:amd64.
Preparing to unpack .../linux-libc-dev_3.16.7-2_amd64.deb ...
Unpacking linux-libc-dev:amd64 (3.16.7-2) ...
Selecting previously unselected package libc6-dev:amd64.
Preparing to unpack .../libc6-dev_2.19-13_amd64.deb ...
Unpacking libc6-dev:amd64 (2.19-13) ...
Selecting previously unselected package zlib1g-dev:amd64.
Preparing to unpack .../zlib1g-dev_1%3a1.2.8.dfsg-2+b1_amd64.deb ...
Unpacking zlib1g-dev:amd64 (1:1.2.8.dfsg-2+b1) ...
Selecting previously unselected package libphobos-4.8-dev.
Preparing to unpack .../libphobos-4.8-dev_4.8.3-15_amd64.deb ...
Unpacking libphobos-4.8-dev (4.8.3-15) ...
Selecting previously unselected package libphobos-4.9-dev.
Preparing to unpack .../libphobos-4.9-dev_4.9.2-4_amd64.deb ...
Unpacking libphobos-4.9-dev (4.9.2-4) ...
dpkg: error processing archive /var/cache/apt/archives/libphobos-4.9-dev_4.9.2-4_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libgphobos2.a', which is also in package libphobos-4.8-dev 4.8.3-15
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for man-db (2.7.0.2-3) ...
Errors were encountered while processing:
/var/cache/apt/archives/libphobos-4.9-dev_4.9.2-4_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/lib/x86_64-linux-gnu/libgphobos2.a
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/.
Reply to: