Package: duplicity
Version: 0.6.06-2
Severity: normal
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32.2 (PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages duplicity depends on:
ii gnupg 1.4.10-2 GNU privacy guard - a free PGP rep
ii libc6 2.10.2-2 GNU C Library: Shared libraries
ii librsync1 0.9.7-7 rsync remote-delta algorithm libra
ii python 2.5.4-5 An interactive high-level object-o
ii python-central 0.6.14+nmu2 register and build utility for Pyt
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
Duplicity reasonably seams to assume that incremental backups encrypted against
a public key do not require a passphrase, but apparently this assumption is not
true.
So
duplicity --encrypt-key XXXXXXXX test file://testbackup
succeeds in creating a full backup but reissuing the command, i.e. creating an
incremental backup fails with
GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: verschlüsselt mit 4096-Bit ELG-E Schlüssel, ID XXXXXXXX, erzeugt 2007-08-17
"Konrad Zimmermann (E-Mail) <XXXXXXXXXXXX>"
gpg: Entschlüsselung mit Public-Key-Verfahren fehlgeschlagen: Falsche Passphrase
gpg: Entschlüsselung fehlgeschlagen: Geheimer Schlüssel ist nicht vorhanden
===== End GnuPG log =====
The -v 9 option reveals the following traceback
GPG error detail: Traceback (most recent call last):
File "/usr/bin/duplicity", line 1236, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1229, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1210, in main
check_last_manifest(col_stats) # not needed for full backup
File "/usr/bin/duplicity", line 970, in check_last_manifest
last_backup_set.check_manifests()
File "/usr/lib/python2.5/site-packages/duplicity/collections.py", line 180,
in check_manifests
remote_manifest = self.get_remote_manifest()
File "/usr/lib/python2.5/site-packages/duplicity/collections.py", line 214,
in get_remote_manifest
manifest_buffer = self.backend.get_data(self.remote_manifest_name)
File "/usr/lib/python2.5/site-packages/duplicity/backend.py", line 490, in
get_data
assert not fin.close()
File "/usr/lib/python2.5/site-packages/duplicity/dup_temp.py", line 210, in
close
assert not self.fileobj.close()
File "/usr/lib/python2.5/site-packages/duplicity/gpg.py", line 201, in close
self.gpg_failed()
File "/usr/lib/python2.5/site-packages/duplicity/gpg.py", line 168, in
gpg_failed
raise GPGError, msg
As a workaround one ca force duplicity to ask for the passphrase with the
--sign-key option and the same key. Doing this the incremental backups will
succeed.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
