Your message dated Sat, 29 Nov 2025 14:41:57 +1000
with message-id <[email protected]>
and subject line duplicity ancient bug housecleaning
has caused the Debian Bug report #606182,
regarding duplicity: Fails with cryptic gpg: decrypt_message failed: eof
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.)
--
606182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606182
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: duplicity
Version: 0.6.15-4
Severity: normal
Hi.
I don't know what happened (may be linked to a filesystem full recently), but
some of my duplicity backups started failing with :
...
No orphaned or incomplete backup sets found.
GnuPG passphrase:
Retype passphrase to confirm:
PASSPHRASE variable not set, asking user.
Registering (mktemp) temporary file
/tmp/duplicity-K5Fs72-tempdir/mktemp-WPeIYO-2
Running 'sftp -oServerAliveInterval=15 -oServerAliveCountMax=2
backup@backuphost' (attempt #1)
State = sftp, Before = 'Connected to backuphost.'
sftp command: 'get
"/mnt/testbackups/slash/duplicity-full.20111216T002932Z.manifest.gpg"
"/tmp/duplicity-K5Fs72-tempdir/mktemp-WPeIYO-2"'
State = sftp, Before = 'get
"/mnt/testbackups/slash/duplicity-full.20111216T002932Z.manifest.gpg"
"/tmp/duplicity-K5Fs72-tempdir/mktemp-WPeIYO-2"
Fetching /mnt/testbackups/slash/duplicity-full.20111216T002932Z.manifest.gpg to
/tmp/duplicity-K5Fs72-tempdir/mktemp-WPeIYO-2'
State = sftp, Before = 'quit'
Removing still remembered temporary file
/tmp/duplicity-K5Fs72-tempdir/mktemp-WPeIYO-2
Removing still remembered temporary file
/tmp/duplicity-K5Fs72-tempdir/mkstemp-6J075i-1
GPG error detail: Traceback (most recent call last):
File "/usr/bin/duplicity", line 1344, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1327, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1308, in main
check_last_manifest(col_stats) # not needed for full backup
File "/usr/bin/duplicity", line 1048, in check_last_manifest
last_backup_set.check_manifests()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 182,
in check_manifests
remote_manifest = self.get_remote_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 216,
in get_remote_manifest
manifest_buffer = self.backend.get_data(self.remote_manifest_name)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 544, in
get_data
assert not fin.close()
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 214, in
close
assert not self.fileobj.close()
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 213, in close
self.gpg_failed()
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 180, in
gpg_failed
raise GPGError, msg
GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: decrypt_message failed: eof
===== End GnuPG log =====
GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: decrypt_message failed: eof
===== End GnuPG log =====
I think it would be great if duplicity detected what goes wrong before that
strange GPG error...
Thanks in advance.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (650, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.1.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages duplicity depends on:
ii libc6 2.13-23
ii librsync1 0.9.7-8
ii python 2.7.2-9
ii python-gnupginterface 0.3.2-9.1
ii python-pexpect 2.3-1
ii python2.7 2.7.2-8
duplicity recommends no packages.
Versions of packages duplicity suggests:
pn ncftp 2:3.2.5-1
pn python-boto <none>
pn rsync 3.0.9-1
pn ssh <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
as far as i can tell these 10+ year old bugs are closable,
because they're either no longer relevant (pretty different OS environment),
or never received the requested moreinfo followup,
or were not directly related to duplicity itself (ie. applied
to various dependencies),
or were fixed at some point in the past 10+ years without me noting.
regards
az
--
Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + https://snafu.priv.at/
Es ist nichts so absurd, daß Gläubige es nicht glaubten.
Oder Beamte täten. -- Arno Schmidt
signature.asc
Description: Digital Signature
--- End Message ---
