Version interoperability.

There were some minor tweaks to the manifest file format to support
restart operations in the latest revisions. Going backwards may be a
problem, but going forwards should not be a problem.

dcaban wrote:
> New question #115018 on Duplicity:
> https://answers.launchpad.net/duplicity/+question/115018
>
> Is there any reason duplicity 0.4.10 would not archive remote files from a duplicity 0.6.08b installation that had saved a backup to a local directory?
>
>

Thank you for the prompt reply.

So are these changes consistent with the following output:

4 files exist on backend
Extracting backup chains from list of files: ['duplicity-full-signatures.20100618T141947Z.sigtar.gpg', 'duplicity-full.20100618T141947Z.manifest.gpg', 'duplicity-full.20100618T141947Z.vol1.difftar.gpg', 'duplicity-full.20100618T141947Z.vol2.difftar.gpg']
File duplicity-full-signatures.20100618T141947Z.sigtar.gpg is not part of a known set; creating new set
Ignoring file (rejected by backup set) 'duplicity-full-signatures.20100618T141947Z.sigtar.gpg'
File duplicity-full.20100618T141947Z.manifest.gpg is not part of a known set; creating new set
Ignoring file (rejected by backup set) 'duplicity-full.20100618T141947Z.manifest.gpg'
File duplicity-full.20100618T141947Z.vol1.difftar.gpg is not part of a known set; creating new set
Ignoring file (rejected by backup set) 'duplicity-full.20100618T141947Z.vol1.difftar.gpg'
File duplicity-full.20100618T141947Z.vol2.difftar.gpg is not part of a known set; creating new set
Ignoring file (rejected by backup set) 'duplicity-full.20100618T141947Z.vol2.difftar.gpg'
Collection Status
-----------------
Connecting with backend: sshBackend
Archive dir: None

Found 0 backup chains without signatures.
No backup chains with active signatures found
No orphaned or incomplete backup sets found.
Last full backup date: none
Using temporary directory /tmp/duplicity-RI5izc-tempdir
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 463, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 458, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 428, in main
    restore(col_stats)
  File "/usr/bin/duplicity", line 206, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/usr/bin/duplicity", line 221, in restore_get_patched_rop_iter
    backup_chain = col_stats.get_backup_chain_at_time(time)
  File "/usr/lib/python2.5/site-packages/duplicity/collections.py", line 717, in get_backup_chain_at_time
    raise CollectionsError("No backup chains found")
duplicity.collections.CollectionsError: No backup chains found

Thanks Kenneth Loafman, that solved my question.

I just wanted to add this comment for the benefit of others.

I forced an upgrade to have both version running at duplicity 0.6.08b.

The exact same restore command worked perfectly!