Package: duplicity
Version: 0.6.15-4
Severity: normal

It could be impossible to backup to limited filesize backend, like imap, or
ftp.

The last generated file (duplicity-full-signatures.*.sigtar.gpg) can be easily
bigger than the limited filesize of the backend. This will result in a backup
fail.
The signature and manifest archive should be split to respect the volume size's
command line option.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages duplicity depends on:
ii  libc6                  2.13-21  
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-5  

duplicity recommends no packages.

Versions of packages duplicity suggests:
pn  ncftp        <none> 
pn  python-boto  2.0-2  
pn  rsync        3.0.9-1
pn  ssh          <none> 

-- no debconf information



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

Reply via email to