Your message dated Mon, 04 Jul 2011 06:40:11 +0000
with message-id <e1qdcph-0004z3...@franck.debian.org>
and subject line Bug#632473: fixed in s3ql 1.0.1-2
has caused the Debian Bug report #632473,
regarding s3ql: file conflict with pcp
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.)


-- 
632473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: s3ql
Version: 1.0.1-1
Severity: serious
Justification: Policy 6.6(4)

s3ql is impossible to install alongside pcp:

Unpacking s3ql (from .../archives/s3ql_1.0.1-1_all.deb) ...
dpkg: error processing /var/cache/apt/archives/s3ql_1.0.1-1_all.deb (--unpack):
 trying to overwrite '/usr/share/man/man1/pcp.1.gz', which is also in package 
pcp 3.5.2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

I'm directing the BTS to send a copy of this report to pcp's
maintainer as well; however, I feel that the older pcp has a better
claim to the name and as such would recommend that s3ql rename its pcp
script (and corresponding man page) to something along the lines of
parallel-cp or s3ql-pcp.

Could you please look into doing so?

Thanks!



--- End Message ---
--- Begin Message ---
Source: s3ql
Source-Version: 1.0.1-2

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

s3ql_1.0.1-2.debian.tar.bz2
  to main/s/s3ql/s3ql_1.0.1-2.debian.tar.bz2
s3ql_1.0.1-2.dsc
  to main/s/s3ql/s3ql_1.0.1-2.dsc
s3ql_1.0.1-2_all.deb
  to main/s/s3ql/s3ql_1.0.1-2_all.deb



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 632...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nikolaus Rath <nikol...@rath.org> (supplier of updated s3ql 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: Sun, 03 Jul 2011 10:44:00 -0400
Source: s3ql
Binary: s3ql
Architecture: source all
Version: 1.0.1-2
Distribution: unstable
Urgency: low
Maintainer: Debian Python Apps Team <python-apps-t...@lists.alioth.debian.org>
Changed-By: Nikolaus Rath <nikol...@rath.org>
Description: 
 s3ql       - Full-featured file system for online data storage
Closes: 632473
Changes: 
 s3ql (1.0.1-2) unstable; urgency=low
 .
   * Install pcp as parallel-cp to avoid file name conflict with
     pcp ("Performance Co-Pilot") package. Closes: #632473.
Checksums-Sha1: 
 9bec53adb906789fe026ff86cc0c69aa994abfd4 1555 s3ql_1.0.1-2.dsc
 9204b1852881cec865620db4b7d94cc6a92e6af2 4145 s3ql_1.0.1-2.debian.tar.bz2
 288ca6c2a028e87aca529e6115c73a6d18a8a682 458076 s3ql_1.0.1-2_all.deb
Checksums-Sha256: 
 0ab5f30ec1d13d494d766dc83eea6663a05b4e042defa91c086439d2a8dd69ee 1555 
s3ql_1.0.1-2.dsc
 38dc430e486d1288e7bf783777c9988bb329eab8956a44fae7ec045666b116dc 4145 
s3ql_1.0.1-2.debian.tar.bz2
 ac932e9d809068f03cde2341c7e5819dbca4c0fd363e1f9f9c38cedc897a4080 458076 
s3ql_1.0.1-2_all.deb
Files: 
 e40e36ef0528065f7bf1991a96dccb72 1555 misc optional s3ql_1.0.1-2.dsc
 5136f53ee293f884e2a98f70b7d0c193 4145 misc optional s3ql_1.0.1-2.debian.tar.bz2
 572a39fef01d2936baa0486fb106f6f2 458076 misc optional s3ql_1.0.1-2_all.deb

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

iD8DBQFOEVtnvdkzt4X+wX8RAoCLAJ9+zJ7iXOdTX22pQWnVVKqjPYH6wgCeMFtN
7vHz/POLUJWTqRsG7EL65bY=
=adOP
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to