Your message dated Mon, 17 Oct 2011 13:53:52 +0200
with message-id <20111017135352.687f2983@local>
and subject line Re: [Pkg-javascript-devel] Bug#645601: node-backbone-dirty and
libnode-backbone-dirty: error when trying to install together
has caused the Debian Bug report #645602,
regarding node-chrono and libnode-chrono: 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.)
--
645602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnode-chrono,node-chrono
Version: libnode-chrono/1.0.2-1
Version: node-chrono/1.0.2-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Date: 2011-10-17
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:
WARNING: The following packages cannot be authenticated!
libc-ares2 libicu44 libv8-3.4.14.21 libev4 libnode-chrono nodejs node-chrono
Authentication warning overridden.
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously unselected package libc-ares2.
(Reading database ... 10586 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 libv8-3.4.14.21.
Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-3_amd64.deb) ...
Selecting previously unselected package libev4.
Unpacking libev4 (from .../libev4_1%3a4.04-1_amd64.deb) ...
Selecting previously unselected package libnode-chrono.
Unpacking libnode-chrono (from .../libnode-chrono_1.0.2-1_all.deb) ...
Selecting previously unselected package nodejs.
Unpacking nodejs (from .../nodejs_0.4.12-1_amd64.deb) ...
Selecting previously unselected package node-chrono.
Unpacking node-chrono (from .../node-chrono_1.0.2-2_all.deb) ...
dpkg: error processing /var/cache/apt/archives/node-chrono_1.0.2-2_all.deb
(--unpack):
trying to overwrite '/usr/lib/nodejs/chrono.js', which is also in package
libnode-chrono 1.0.2-1
configured to not write apport reports
Processing triggers for man-db ...
Errors were encountered while processing:
/var/cache/apt/archives/node-chrono_1.0.2-2_all.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/nodejs/chrono.js
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. You may
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 ---
Hello Ralf,
On Mon, 17 Oct 2011 12:54:11 +0200, Ralf Treinen wrote:
> Package: libnode-backbone-dirty,node-backbone-dirty
> Version: libnode-backbone-dirty/1.1.2-1
> Version: node-backbone-dirty/1.1.2-2
> Severity: serious
> User: trei...@debian.org
> Usertags: edos-file-overwrite
>
> [..]
(and much more similar bugs)
libnode-* were renamed node-* while they were in NEW. They were built fromthe
same source, and as you may notice, node-* have a revision of -2, while
libnode-* had -1.
There must've been some problem when they got ACCEPTed, but libnode-* packages
aren't currently built from any source, so they should be removed by the
auto-cruft-removal script.
As you can see, their removals is already scheduled:
http://ftp-master.debian.org/cruft-report-daily.txt
I'm closing these bugs.
David
--
. ''`. Debian developer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 ----|---- http://deb.li/dapal
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
--- End Message ---
