duplicity: list index out of range error when running a restore

[colmtroy@…]

Hi there,

I have installed duplicity 0.6.13 via macports on Mac OS X 10.6.6

Everything works fine until I attempt a restore of a backup from an S3 bucket using the --restore flag.

I get the error shown below.

It's strange because when I look at the restore location, I can see half my files have restored so it looks like a timeout or some hard limit is being reached.

Any ideas what it could be?

Attempting to restore now ...
Traceback (most recent call last):
  File "/opt/local/bin/duplicity", line 1250, in <module>
    with_tempdir(main)
  File "/opt/local/bin/duplicity", line 1243, in with_tempdir
    fn()
  File "/opt/local/bin/duplicity", line 1197, in main
    restore(col_stats)
  File "/opt/local/bin/duplicity", line 539, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/duplicity/patchdir.py", line 523, in Write_ROPaths
    ITR( ropath.index, ropath )
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/duplicity/lazy.py", line 329, in __call__
    if self.finish_branches(index) is None:
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/duplicity/lazy.py", line 272, in finish_branches
    to_be_finished = branches[-1]
IndexError: list index out of range

[jmroot (Joshua Root)]

As per the ticket guidelines linked from the New Ticket page, please don't set the Milestone field, and remember to cc the maintainer.

[jmroot (Joshua Root)]

Is this still a problem with 0.6.18?

[ryandesign (Ryan Carsten Schmidt)]

Is this still a problem with 0.6.21?

[neverpanic (Clemens Lang)]

Is this still a problem with 0.7.01 from r133434? If it is, did you file a ticket upstream?

[ryandesign (Ryan Carsten Schmidt)]

Duplicity is now at 0.7.02. If you still experience this problem, please report it the developers of duplicity; it does not sound like a MacPorts-specific problem.