[Duplicity-talk] Crash at end of backup

[Nick Burch]

I'm using duplicity 0.4.1 to backup some local files, and some from a 
mounted samba share. The local backups work fine, but the backup from the 
samba mount breaks at (what I believe to be) around the end. I'm running

export TMPDIR=/backup6/duplicity-tmp; duplicity -v9 --no-encryption 
--exclude '/mnt/dumbleshare/Temporary Items'  /mnt/dumbleshare 
file:///backup5/dumbledore/dumbleshare-2003-11-23/

And the output I get is:

No signatures found, switching to full backup.
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 358, in ?
    if __name__ == "__main__": main()
  File "/usr/bin/duplicity", line 351, in main
    if not sig_chain: full_backup(col_stats)
  File "/usr/bin/duplicity", line 134, in full_backup
    bytes_written = write_multivol("full", tarblock_iter, globals.backend)
  File "/usr/bin/duplicity", line 76, in write_multivol
    else: at_end = gpg.GzipWriteFile(tarblock_iter, tdp.name)
  File 
"/var/tmp/duplicity-0.4.1-0.fdr.2-root-root/usr/lib/python2.3/site-packages/duplicity/gpg.py",
 line 254, in GzipWriteFile
  File 
"/var/tmp/duplicity-0.4.1-0.fdr.2-root-root/usr/lib/python2.3/site-packages/duplicity/diffdir.py",
 line 407, in next
  File 
"/var/tmp/duplicity-0.4.1-0.fdr.2-root-root/usr/lib/python2.3/site-packages/duplicity/diffdir.py",
 line 487, in process
  File 
"/var/tmp/duplicity-0.4.1-0.fdr.2-root-root/usr/lib/python2.3/site-packages/duplicity/diffdir.py",
 line 507, in get_data_block
  File 
"/var/tmp/duplicity-0.4.1-0.fdr.2-root-root/usr/lib/python2.3/site-packages/duplicity/diffdir.py",
 line 338, in read
IOError: [Errno 2] No such file or directory
Main action: inc
Collection Status
-----------------
Backend: <duplicity.backends.LocalBackend instance at 0x4047bc8c>
Archive dir: None
Matched pair: None
All backup chains: []
Other backup chains: []
Other sig chains: []
Orphaned sig names: []
Orphaned backup sets: []
Incomplete backup sets: []
----------------Backup Chains----------------------

(followed by a whole bunch of error free lines on the state of the files 
being backed up)

Anyone know what the problem is, and how to fix it?

Thanks
Nick