[Duplicity-talk] Upgrade/rollback difficulties

[Russell Clemings]

I've been using duplicity-0.6.08b (Python 2.4.3, boto-1.9b, GnuPG 1.4.5) successfully for quite some time, but decided it was time to upgrade. (Famous last words.)

I installed duplicity-0.6.25 and boto-2.1.1 and after resolving some new dependencies, I got the following when I tried to run a backup:

---------------------------------------------

address@hidden [/path/to/scripts/s3backup]# ./backup.sh

Import of duplicity.backends.cloudfilesbackend Failed: the scheme cf+http already has a backend associated with it

Traceback (most recent call last):

  File "/usr/bin/duplicity", line 1239, in ?

    with_tempdir(main)

  File "/usr/bin/duplicity", line 1232, in with_tempdir

    fn()

  File "/usr/bin/duplicity", line 1118, in main

    action = "">

  File "/usr/lib/python2.4/site-packages/duplicity/commandline.py", line 1062, in ProcessCommandLine

    backup, local_pathname = set_backend(args[0], args[1])

  File "/usr/lib/python2.4/site-packages/duplicity/commandline.py", line 955, in set_backend

    globals.backend = backend.get_backend(bend)

  File "/usr/lib/python2.4/site-packages/duplicity/backend.py", line 163, in get_backend

    return _backends[pu.scheme](pu)

  File "/usr/lib/python2.4/site-packages/duplicity/backends/_boto_single.py", line 163, in __init__

    self.resetConnection()

  File "/usr/lib/python2.4/site-packages/duplicity/backends/_boto_single.py", line 185, in resetConnection

    self.conn = get_connection(self.scheme, self.parsed_url, self.storage_uri)

  File "/usr/lib/python2.4/site-packages/duplicity/backends/_boto_single.py", line 38, in get_connection

    from boto.s3.connection import S3Connection

  File "/usr/lib/python2.4/site-packages/boto-2.1.1-py2.4.egg/boto/s3/connection.py", line 292

    delimiter = '?' if '?' not in auth_path else '&'

                     ^

SyntaxError: invalid syntax

---------------------------------------------

So I cleaned out all of the new duplicity and boto files and reinstalled the old versions.

It started up just fine but then quit as follows:

---------------------------------------------

address@hidden [/path/to/scripts/s3backup]# ./backup.sh

Synchronizing remote metadata to local cache...

Copying duplicity-full-signatures.20141025T050704Z.sigtar to local cache.

Copying duplicity-full.20140928T050703Z.manifest to local cache.

Copying duplicity-full.20141025T050704Z.manifest to local cache.

Copying duplicity-inc.20140928T050703Z.to.20140929T040702Z.manifest to local cache.

(and so on ... snipped a long list of files)

Copying duplicity-inc.20141027T040702Z.to.20141028T040704Z.manifest to local cache.

Copying duplicity-new-signatures.20141025T050704Z.to.20141026T040703Z.sigtar to local cache.

Copying duplicity-new-signatures.20141026T040703Z.to.20141027T040702Z.sigtar to local cache.

Copying duplicity-new-signatures.20141027T040702Z.to.20141028T040704Z.sigtar to local cache.

Traceback (most recent call last):

  File "/usr/bin/duplicity", line 1239, in ?

    with_tempdir(main)

  File "/usr/bin/duplicity", line 1232, in with_tempdir

    fn()

  File "/usr/bin/duplicity", line 1137, in main

    globals.archive_dir).set_values()

  File "/usr/lib/python2.4/site-packages/duplicity/collections.py", line 679, in set_values

    (backup_chains, self.orphaned_backup_sets,

  File "/usr/lib/python2.4/site-packages/duplicity/collections.py", line 804, in get_backup_chains

    map(add_to_sets, filename_list)

  File "/usr/lib/python2.4/site-packages/duplicity/collections.py", line 794, in add_to_sets

    if set.add_filename(filename):

  File "/usr/lib/python2.4/site-packages/duplicity/collections.py", line 89, in add_filename

    self.set_manifest(filename)

  File "/usr/lib/python2.4/site-packages/duplicity/collections.py", line 117, in set_manifest

    assert not self.remote_manifest_name, (self.remote_manifest_name,

AssertionError: ('duplicity-full.20140928T050703Z.manifest.gpg', 'duplicity-full.20140928T050703Z.manifest.gpg')

---------------------------------------------

I'd appreciate some guidance on resolving the second error so that I can get my backups going again.

After that, I may try the upgrade again, so any advice on the first error would be useful as well.

rac