(I apologize if you get two copies of this message. I sent one
yesterday, but I wasn't subscribed and didn't see it in the archives,
so I wasn't sure if it arrived.)
I'm trying to back up most of my home directory to an rsync.net
filesystem. I've made two full backups, and now whenever I try to do
anything with the destination directory, I get an error:
address@hidden ~ $ duplicity -v9 --collection-status
scp://address@hidden/backups/lion-home/
Main action: collection-status
Reading results of 'printf 'cd backups/lion-home/
ls -1' | sftp -oPort=22 -b - address@hidden'
Ignoring file
'duplicity-full-signatures.2007-06-24T02:02:08-04:00.sigtar.gpg'
Ignoring file
'duplicity-full-signatures.2007-06-25T02:01:25-04:00.sigtar.gpg'
Traceback (most recent call last):
File "/usr/local/bin/duplicity", line 378, in ?
if __name__ == "__main__": main()
File "/usr/local/bin/duplicity", line 354, in main
globals.archive_dir).set_values()
File "/usr/local/lib64/python2.4/site-packages/duplicity/collections.py",
line 420, in set_values
backup_chains)
File "/usr/local/lib64/python2.4/site-packages/duplicity/collections.py",
line 443, in set_matched_chain_pair
elif sig_chains[i].end_time ==
latest_backup_chain.get_all_sets()[-2].end_time:
IndexError: list index out of range
Here's what's in the remote directory:
address@hidden ~ $ ssh address@hidden ls backups/lion-home
duplicity-full-signatures.2007-06-24T02:02:08-04:00.sigtar.gpg
duplicity-full-signatures.2007-06-25T02:01:25-04:00.sigtar.gpg
duplicity-full.2007-06-24T02:02:08-04:00.manifest.gpg
duplicity-full.2007-06-24T02:02:08-04:00.vol1.difftar.gpg
duplicity-full.2007-06-24T02:02:08-04:00.vol10.difftar.gpg
duplicity-full.2007-06-24T02:02:08-04:00.vol11.difftar.gpg
duplicity-full.2007-06-24T02:02:08-04:00.vol12.difftar.gpg
duplicity-full.2007-06-24T02:02:08-04:00.vol13.difftar.gpg
duplicity-full.2007-06-24T02:02:08-04:00.vol2.difftar.gpg
duplicity-full.2007-06-24T02:02:08-04:00.vol3.difftar.gpg
duplicity-full.2007-06-24T02:02:08-04:00.vol4.difftar.gpg
duplicity-full.2007-06-24T02:02:08-04:00.vol5.difftar.gpg
duplicity-full.2007-06-24T02:02:08-04:00.vol6.difftar.gpg
duplicity-full.2007-06-24T02:02:08-04:00.vol7.difftar.gpg
duplicity-full.2007-06-24T02:02:08-04:00.vol8.difftar.gpg
duplicity-full.2007-06-24T02:02:08-04:00.vol9.difftar.gpg
duplicity-full.2007-06-25T02:01:25-04:00.manifest.gpg
duplicity-full.2007-06-25T02:01:25-04:00.vol1.difftar.gpg
duplicity-full.2007-06-25T02:01:25-04:00.vol10.difftar.gpg
duplicity-full.2007-06-25T02:01:25-04:00.vol11.difftar.gpg
duplicity-full.2007-06-25T02:01:25-04:00.vol12.difftar.gpg
duplicity-full.2007-06-25T02:01:25-04:00.vol13.difftar.gpg
duplicity-full.2007-06-25T02:01:25-04:00.vol2.difftar.gpg
duplicity-full.2007-06-25T02:01:25-04:00.vol3.difftar.gpg
duplicity-full.2007-06-25T02:01:25-04:00.vol4.difftar.gpg
duplicity-full.2007-06-25T02:01:25-04:00.vol5.difftar.gpg
duplicity-full.2007-06-25T02:01:25-04:00.vol6.difftar.gpg
duplicity-full.2007-06-25T02:01:25-04:00.vol7.difftar.gpg
duplicity-full.2007-06-25T02:01:25-04:00.vol8.difftar.gpg
duplicity-full.2007-06-25T02:01:25-04:00.vol9.difftar.gpg
I'm running Duplicity 0.4.3-RC7.
Any help you can offer would be greatly appreciated. I apologize if
this is just a mistake I made.
Thanks,
Thomas Tuttle