Your message dated Sun, 31 Aug 2008 02:47:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#497071: fixed in duplicity 0.4.12-2
has caused the Debian Bug report #497071,
regarding duplicity: prompts for GnuPG passphrase with --no-encryption, can 
break cronjobs
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 [EMAIL PROTECTED]
immediately.)


-- 
497071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497071
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: duplicity
Version: 0.4.12-1
Severity: normal

Hi,

I noticed that the new version of duplicity prompts for the GnuPG passphrase
even if it is used with --no-encryption:

$ duplicity full --no-encryption . file:///tmp/
GnuPG passphrase:
Retype passphrase to confirm:
Cannot use empty passphrase with symmetric encryption!  Please try again.
GnuPG passphrase:
Retype passphrase to confirm:

[...]

$ duplicity incremental --no-encryption . file:///tmp/
GnuPG passphrase:

The program seems to accept any non-empty passphrase and it correctly
creates unencrypted *.gz files in the end, but the prompting for the
passphrase is problematic for cronjobs (and for use in other
non-interactive scripts, I suppose).

I found this upstream bug: http://savannah.nongnu.org/bugs/?23985

Until upstream fixes this bug there is a simple workaround: I now use

export PASSPHRASE=

in my cronjob scripts before "duplicity --no-encryption ..." is invoked;
this is sufficient to suppress the passphrase prompt.

Thank you for your time.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-flo (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages duplicity depends on:
ii  gnupg                         1.4.9-3    GNU privacy guard - a free PGP rep
ii  libc6                         2.7-13     GNU C Library: Shared libraries
ii  librsync1                     0.9.7-5    rsync remote-delta algorithm libra
ii  python                        2.5.2-2    An interactive high-level object-o
ii  python-central                0.6.8      register and build utility for Pyt
ii  python-gnupginterface         0.3.2-9    Python interface to GnuPG (GPG)
ii  python-pexpect                2.3-1      Python module for automating inter

duplicity recommends no packages.

Versions of packages duplicity suggests:
pn  ncftp                         <none>     (no description available)
pn  python-boto                   <none>     (no description available)

-- no debconf information



--- End Message ---
--- Begin Message ---
Source: duplicity
Source-Version: 0.4.12-2

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

duplicity_0.4.12-2.diff.gz
  to pool/main/d/duplicity/duplicity_0.4.12-2.diff.gz
duplicity_0.4.12-2.dsc
  to pool/main/d/duplicity/duplicity_0.4.12-2.dsc
duplicity_0.4.12-2_i386.deb
  to pool/main/d/duplicity/duplicity_0.4.12-2_i386.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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexander Zangerl <[EMAIL PROTECTED]> (supplier of updated duplicity 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 [EMAIL PROTECTED])


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

Format: 1.8
Date: Sun, 31 Aug 2008 12:24:40 +1000
Source: duplicity
Binary: duplicity
Architecture: source i386
Version: 0.4.12-2
Distribution: unstable
Urgency: low
Maintainer: Alexander Zangerl <[EMAIL PROTECTED]>
Changed-By: Alexander Zangerl <[EMAIL PROTECTED]>
Description: 
 duplicity  - encrypted bandwidth-efficient backup
Closes: 497071
Changes: 
 duplicity (0.4.12-2) unstable; urgency=low
 .
   * applied upstream patch to repair --no-encryption option
     (which wrongly requested a passphrase) (closes: #497071)
Checksums-Sha1: 
 21f1cb2974af525797e5d13406092dc3bcbc3eeb 1053 duplicity_0.4.12-2.dsc
 ec732d15bad1bb57299370dfd33169f8e179c328 9341 duplicity_0.4.12-2.diff.gz
 5a01eecdbd48431be2a6fef7a39c4463fcc64f0b 128468 duplicity_0.4.12-2_i386.deb
Checksums-Sha256: 
 499165eccd68abe3ede8616a730f96c56bea12fe7c9926ec47f9c105c01cc9c3 1053 
duplicity_0.4.12-2.dsc
 00e1703072a5bed1ed1c5b603324baa4c4cfcd3e18a23350bc8b9dbb2ac08916 9341 
duplicity_0.4.12-2.diff.gz
 91a2afaafd93285377f0f57295f337992b6f8624d0b12efc91ab474c7a1b94a9 128468 
duplicity_0.4.12-2_i386.deb
Files: 
 8b2ea5a50504db63286107c81521b98a 1053 utils optional duplicity_0.4.12-2.dsc
 3ca34081fe207e9a16dfe9d2beae743c 9341 utils optional duplicity_0.4.12-2.diff.gz
 80831dc9d1f7b0b6e50dbdfdbd11c232 128468 utils optional 
duplicity_0.4.12-2_i386.deb

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

iD8DBQFIugTRpy/2bEK9ZF0RAgmdAJ9aRNkaI7nKq02m9JUubybrDTkZmgCfQyQs
6sXzFJFrA5tRbJsQtCEuHTI=
=h7Hr
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to