Your message dated Fri, 28 Oct 2011 21:47:54 +0000
with message-id <e1rjuhk-00016b...@franck.debian.org>
and subject line Bug#646933: fixed in step.js 0.0.4-2
has caused the Debian Bug report #646933,
regarding node-step and libnode-step: 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.)


-- 
646933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnode-step,node-step
Version: libnode-step/0.0.4-1
Version: node-step/0.0.4-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2011-10-28
Architecture: amd64
Distribution: sid

[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.]


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 libev4 libv8-3.4.14.21 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-3.4.14.21.
Unpacking libv8-3.4.14.21 (from .../libv8-3.4.14.21_3.4.14.21-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:
 /var/cache/apt/archives/node-step_0.0.4-1_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/step.js

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/.



--- End Message ---
--- Begin Message ---
Source: step.js
Source-Version: 0.0.4-2

We believe that the bug you reported is fixed in the latest version of
step.js, which is due to be installed in the Debian FTP archive:

node-step_0.0.4-2_all.deb
  to main/s/step.js/node-step_0.0.4-2_all.deb
step.js_0.0.4-2.debian.tar.gz
  to main/s/step.js/step.js_0.0.4-2.debian.tar.gz
step.js_0.0.4-2.dsc
  to main/s/step.js/step.js_0.0.4-2.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 646...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
David Paleino <da...@debian.org> (supplier of updated step.js package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Fri, 28 Oct 2011 23:29:43 +0200
Source: step.js
Binary: node-step
Architecture: source all
Version: 0.0.4-2
Distribution: unstable
Urgency: low
Maintainer: Debian Javascript Maintainers 
<pkg-javascript-devel@lists.alioth.debian.org>
Changed-By: David Paleino <da...@debian.org>
Description: 
 node-step  - simple control-flow library for Node
Closes: 646933
Changes: 
 step.js (0.0.4-2) unstable; urgency=low
 .
   * Team upload.
   * Rename binary package from libnode-step to node-step, as per
     Debian Javascript Policy (Closes: #646933)
Checksums-Sha1: 
 10a58ca5615b7bb10842c0962a82e3911f7cf099 1275 step.js_0.0.4-2.dsc
 8b63c61376d6bd787de0b7af8aeed62ff45658d7 3192 step.js_0.0.4-2.debian.tar.gz
 cee10fe9947a91f8fa2d488a76ffb9392254be20 6260 node-step_0.0.4-2_all.deb
Checksums-Sha256: 
 06bad0c5b5c2372450bd46e74b4f5d244ad92049f4fe84b04c8b57434df0f809 1275 
step.js_0.0.4-2.dsc
 0d2b2c985c576e6e885ac09704b1b5d414808d18baace34fa7f2f5cdb0804e65 3192 
step.js_0.0.4-2.debian.tar.gz
 4d5f41cfead5ea029d011c8f73d23b315e20158d2e5253bd19e704ca095636ac 6260 
node-step_0.0.4-2_all.deb
Files: 
 95a6b85c31c597040ba0968a7d7044b1 1275 web optional step.js_0.0.4-2.dsc
 fd40b41260fed2e30a7e463361b9b273 3192 web optional 
step.js_0.0.4-2.debian.tar.gz
 1bb9c803cdb2316e683e986017cd62e6 6260 web optional node-step_0.0.4-2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk6rHygACgkQ5qqQFxOSsXSw5wCffZNjvcDIBVLTVU8d/9QB5Wqd
hLMAn0V8Wd8JJWnjHEE5ee6mmwrDaanb
=PcCe
-----END PGP SIGNATURE-----



--- End Message ---
_______________________________________________
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Reply via email to