[Duplicity-talk] Strange crash ``Bad tarinfo name ././@LongLink''

[Jacob Luna Lundberg]

I was running a full mode backup of about 1GiB and it stopped after only
about 438MiB (it does this repeatably, no error displayed).  When I ask
for a file list (duplicity --list-current-files) it crashes a ways into
the list with this error.

I guess the crash might be related to the incomplete set of archives?
Does anybody have an idea why it would stop partway?

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 352, in ?
    if __name__ == "__main__": main()
  File "/usr/bin/duplicity", line 335, in main
    elif action == "list-current": list_current(col_stats)
  File "/usr/bin/duplicity", line 174, in list_current
    for path in path_iter: print path.get_relative_path()
  File 
"/usr/local/src/duplicity-0.4.0/debian/duplicity/usr/lib/python2.2/site-packages/duplicity/diffdir.py",
 line 234, in combine_path_iters
  File 
"/usr/local/src/duplicity-0.4.0/debian/duplicity/usr/lib/python2.2/site-packages/duplicity/diffdir.py",
 line 222, in refresh_triple_list
  File 
"/usr/local/src/duplicity-0.4.0/debian/duplicity/usr/lib/python2.2/site-packages/duplicity/diffdir.py",
 line 211, in get_triple
  File 
"/usr/local/src/duplicity-0.4.0/debian/duplicity/usr/lib/python2.2/site-packages/duplicity/diffdir.py",
 line 145, in sigtar2path_iter
duplicity.diffdir.DiffDirException: Bad tarinfo name ././@LongLink

Thanks,
-Jacob

-- 

"(Damn! 15 second lockups? That's just not much fun any more.)"
 -Linus Torvalds, Thu, 6 Mar 2003