[Duplicity-talk] Getting an OverflowError when trying to restore backups

[Aaron Barnes]

I'm in a bit of a sticky situation here.   I'm attempting to recover a system that had backups made with duplicity, and it's failing 1/3 of the way through the backup with the following error:

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 825, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 818, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 775, in main
    restore(col_stats)
  File "/usr/bin/duplicity", line 436, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib/python2.5/site-packages/duplicity/patchdir.py", line 521, in Write_ROPaths
    ITR(ropath.index, ropath)
  File "/usr/lib/python2.5/site-packages/duplicity/lazy.py", line 336, in __call__
    last_branch.fast_process, args)
  File "/usr/lib/python2.5/site-packages/duplicity/robust.py", line 38, in check_common_error
    return function(*args)
  File "/usr/lib/python2.5/site-packages/duplicity/patchdir.py", line 574, in fast_process
    ropath.copy(self.base_path.new_index(index))
  File "/usr/lib/python2.5/site-packages/duplicity/path.py", line 429, in copy
    self.copy_attribs(other)
  File "/usr/lib/python2.5/site-packages/duplicity/path.py", line 436, in copy_attribs
    os.utime(other.name, (time.time(), self.stat.st_mtime))
OverflowError: long int too large to convert to int

it's failing in both 0.6.08b, as well as 0.5.20 which i tried downgrading to after.   Searching the archives it looks like a patch was applied to fix this problem in 0.5.11 (although maybe it's a different problem), but is definitely occurring again.  I'm not sure what could have caused this (moving from a 64 to a 32 bit system?)

Can anyone help me out with a patch to path.py so that it progresses past the error? (my python's not too good), or are my archives just done for?

I would be eternally thankful,

--aaron