Package: duplicity
Version: 0.4.2-10.1
Followup-For: Bug #346306

Hi everyone,

is there anything being done about this bug? I see that this report is
open for way over a year now, but so far there hasn't been any reply
on this topic.

I still can reproduce this bug in the current 'unstable' version of
duplicity and have been able to do so in every single version since
I started using this software. A typical python output looks like
this:

--------- by cutting here you might damage your screen surface ---------
 
Traceback (most recent call last):                                              
  File "/usr/bin/duplicity", line 373, in ?                                     
    if __name__ == "__main__": main()                                           
  File "/usr/bin/duplicity", line 367, in main                                  
    else: incremental_backup(sig_chain)                                         
  File "/usr/bin/duplicity", line 170, in incremental_backup                    
    bytes_written = write_multivol("inc", tarblock_iter, globals.backend)       
  File "/usr/bin/duplicity", line 89, in write_multivol                         
    backend.put(tdp, dest_filename)                                             
  File "/usr/lib/python2.4/site-packages/duplicity/backends.py", line 349, in   
put                                                                             
    self.error_wrap('storbinary', "STOR "+remote_filename, source_file)         
  File "/usr/lib/python2.4/site-packages/duplicity/backends.py", line 335, in   
error_wrap                                                                      
    except ftplib.all_errors, e: raise BackendException(e)                      
duplicity.backends.BackendException                                             

--------- by cutting here you might damage your screen surface ---------

As there is no way to tell beforehand if this bug will show up or not,
it renders the software pretty much useless for me. A backup you can't
depend on is no backup at all.

Please try at least to look into this matter and tell if there is any
hope for a fix.

Greetings from Stuttgart,

=ToJe=

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages duplicity depends on:
ii  gnupg                       1.4.6-1      GNU privacy guard - a free PGP rep
ii  libc6                       2.3.6.ds1-13 GNU C Library: Shared libraries
ii  librsync1                   0.9.7-1      Library which implements the rsync
ii  python                      2.4.4-2      An interactive high-level object-o
ii  python-central              0.5.12       register and build utility for Pyt
ii  python-gnupginterface       0.3.2-9      Python interface to GnuPG (GPG)

duplicity recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to