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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
