[I know we had a discussion about this kind of bugs. Now the situation seems
to be different since I observed this bug first on 2011/10/24. Since it
still occurs 5 days later I guess that there is something broken now. -Ralf.]
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!
libc-ares2 libicu44 libev4 libv8-126.96.36.199 nodejs libnode-step node-step
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously unselected package libc-ares2.
(Reading database ... 10587 files and directories currently installed.)
Unpacking libc-ares2 (from .../libc-ares2_1.7.5-1_amd64.deb) ...
Selecting previously unselected package libicu44.
Unpacking libicu44 (from .../libicu44_4.4.2-2_amd64.deb) ...
Selecting previously unselected package libev4.
Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ...
Selecting previously unselected package libv8-188.8.131.52.
Unpacking libv8-184.108.40.206 (from .../libv8-220.127.116.11_18.104.22.168-4_amd64.deb) ...
Selecting previously unselected package nodejs.
Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ...
Selecting previously unselected package libnode-step.
Unpacking libnode-step (from .../libnode-step_0.0.4-1_all.deb) ...
Selecting previously unselected package node-step.
Unpacking node-step (from .../node-step_0.0.4-1_all.deb) ...
dpkg: error processing /var/cache/apt/archives/node-step_0.0.4-1_all.deb (--unpack):
trying to overwrite '/usr/lib/nodejs/step.js', which is also in package libnode-step 0.0.4-1
configured to not write apport reports
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, 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 http://edos.debian.net/file-overwrites/.
To UNSUBSCRIBE, email to debian-bugs-rc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org