Package: libcork15,libcork16
Version: libcork15/0.15.0+ds-6
Version: libcork16/0.15.0+ds-7
Severity: serious
Usertags: edos-file-overwrite

Date: 2016-10-19
Architecture: amd64
Distribution: sid


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 libcork15:amd64.
(Reading database ... 10972 files and directories currently installed.)
Preparing to unpack .../libcork15_0.15.0+ds-6_amd64.deb ...
Unpacking libcork15:amd64 (0.15.0+ds-6) ...
Selecting previously unselected package libcork16:amd64.
Preparing to unpack .../libcork16_0.15.0+ds-7_amd64.deb ...
Unpacking libcork16:amd64 (0.15.0+ds-7) ...
dpkg: error processing archive 
/var/cache/apt/archives/libcork16_0.15.0+ds-7_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/', which is 
also in package libcork15:amd64 0.15.0+ds-6
Processing triggers for libc-bin (2.24-5) ...
Errors were encountered while processing:
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):


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.


PS: for more information about the detection of file overwrite errors
of this kind see

Reply via email to