Bug#530450: libelfg0-dev and libbsd-dev: error when trying to install together
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!
libbsd0 libbsd-dev linux-libc-dev libc6-dev libelfg0 libelfg0-dev
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously deselected package libbsd0.
(Reading database ... 8136 files and directories currently installed.)
Unpacking libbsd0 (from .../libbsd0_0.1.1-1_amd64.deb) ...
Selecting previously deselected package libbsd-dev.
Unpacking libbsd-dev (from .../libbsd-dev_0.1.1-1_amd64.deb) ...
Selecting previously deselected package linux-libc-dev.
Unpacking linux-libc-dev (from .../linux-libc-dev_2.6.29-5_amd64.deb) ...
Selecting previously deselected package libc6-dev.
Unpacking libc6-dev (from .../libc6-dev_2.9-12_amd64.deb) ...
Selecting previously deselected package libelfg0.
Unpacking libelfg0 (from .../libelfg0_0.8.10-2_amd64.deb) ...
Selecting previously deselected package libelfg0-dev.
Unpacking libelfg0-dev (from .../libelfg0-dev_0.8.10-2_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/libelfg0-dev_0.8.10-2_amd64.deb (--unpack):
trying to overwrite `/usr/include/nlist.h', which is also in package libbsd-dev
Processing triggers for man-db ...
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. Possible
solutions are to have the two packages conflict, to rename the common
file in one of the two packages, or to remove the file from one
package and have this package depend on the other package. File
diversions or a Replace relation are another possibility.
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 is assigned to 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.