Package: duplicity Version: 0.4.1-8 Severity: important -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I was uploading a large set of files over a slow connection, but after a few hundred megs, the connection was lost. When I ran the backup again, Duplicity noticed that there were incomplete files, probably from an aborted transfer, but it started backing up *everything* from scratch. It seems to me Duplicity should: 1. Try to reestablish the connection immediately, and resume the last transfer, instead of generating an exception and exiting. It would be nice if there were command-line options for number of retries and connection timeouts. 2. If the connection fails completely, and Duplicity finally has to exit, it should try to resume the backup the next time it is run, rather than starting from scratch. This is resulting in gigs of files having to be needlessly retransferred. I know rsync would handle this properly, but rsync can't store files encrypted on the destination. - -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13-1-k7 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages duplicity depends on: ii gnupg 1.4.2-2 GNU privacy guard - a free PGP rep ii libc6 2.3.5-8 GNU C Library: Shared libraries an ii librsync1 0.9.7-1 Library which implements the rsync ii python-gnupginterface 0.3.2-7 Python interface to GnuPG (GPG) ii python2.3 2.3.5-8 An interactive high-level object-o duplicity recommends no packages. - -- no debconf information -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDvule5+GdyTDsrJsRAsrXAKDEfsJ+UnVBo5y3RKpdmeXmcpg+0QCfb6wF hgJ123tZsfgLqsHrKp8Cu6A= =uEA1 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
