Bug#706767: duplicity: Fails deleting remote (sftp) backup chains

[Olivier Berger]

Package: duplicity
Version: 0.6.20-3
Severity: normal

Hi.

I have problems removing remote backup chains.

For instance (run in a backupninja handler) :
Debug: duplicity remove-older-than 35D --force --no-print-statistics
--ssh-options '' --full-if-older-than 30D --extra-clean --archive-dir
/var/cache/backupninja/duplicity
scp://auser@aremotehost/whaeverdir

Debug: Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Tue Apr 16 02:56:47 2013
Deleting backup chain at time: Fri Mar 22 03:49:11 2013
Deleting complete backup chain Fri Mar 22 03:49:11 2013
sftp rm duplicity-inc.20130321T000449Z.to.20130322T024911Z.manifest.gpg failed:
[Errno 2] No such file (Try 2 of 5) Will retry in 10 seconds.
sftp rm duplicity-inc.20130321T000449Z.to.20130322T024911Z.manifest.gpg failed:
[Errno 2] No such file (Try 3 of 5) Will retry in 10 seconds.
sftp rm duplicity-inc.20130321T000449Z.to.20130322T024911Z.manifest.gpg failed:
[Errno 2] No such file (Try 4 of 5) Will retry in 10 seconds.
sftp rm duplicity-inc.20130321T000449Z.to.20130322T024911Z.manifest.gpg failed:
[Errno 2] No such file
Warning: Duplicity remove-older-than failed.

It seems that after a while and removal of the cache (/var/cache/backupninja/duplicity), it will eventually stop complaining.

I suspect this may be the same issue as in https://bugs.launchpad.net/duplicity/+bug/1031269 which is fixed in 0.6.21 upstream.

Would you care to tell me how I could generate a test package of 0.6.21, assuming that not much changed wrt 0.6.20 ?

Many thanks in advance.

Best regards,

-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages duplicity depends on:
ii libc6 2.13-38
ii librsync1 0.9.7-9
ii python 2.7.3-4

Versions of packages duplicity recommends:
ii python-httplib2 0.7.4-2
ii python-oauth 1.0.1-3
ii python-paramiko 1.7.7.1-3.1
ii rsync 3.0.9-4

Versions of packages duplicity suggests:
ii lftp 4.3.8-1.1
ii ncftp 2:3.2.5-1.1
pn python-boto <none>
pn python-cloudfiles <none>
ii python-gdata 2.0.17+dfsg-1
ii python-pexpect 2.4-1
pn tahoe-lafs <none>

-- no debconf information


--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

[Alexander Zangerl]

On Sat, 04 May 2013 16:19:10 +0200, Olivier Berger writes:
>Would you care to tell me how I could generate a test package of 0.6.21,
>assuming that not much changed wrt 0.6.20 ?

first up i haven't looked at .21 yet, so i don't really know the extent
of the changes. if they did nothing drastic then an apt-get source duplicity
followed by uscan and uupdate in the .20 dir and a
dpkg-buildpackage -rfakeroot -us -uc (in the .21 dir that uupdate creates)
should give you something workable.

i'll do my best to package .21 in the next few days.

regards
az


--
Alexander Zangerl + GPG Key 0x42BD645D or 0x5B586291 + http://snafu.priv.at/
"Usenet is like a herd of performing elephants with diarrhea -- massive, dif-
ficult to redirect, awe-inspiring, entertaining, and a source of mindboggling
amounts of excrement when you least expect it." -- Gene Spafford (1992)