Errors if remote listing not in sync with contents

[Matthew]

Duplicity 0.6.24 or 0.7.06, Python 2.7.3, Debian wheezy.

We are currently in a situation with a back up provider where for over a week the directory listing is not in sync with the contents of the directory. This manifests itself in that the oldest duplicity file, call it dbname.server.pg/duplicity-full-signatures.20151120T052121Z.sigtar.gpg is returned in the backend's list() call, but then the copy_to_local of that file fails (as the file is not there, presumably having been deleted the day before as the oldest backup).

This means we are unable to perform a new backup or a clean; with duplicity 0.7.06, you get the following:

    $ duplicity … clean cf+http://dbname.server.pg
    Synchronizing remote metadata to local cache...
    Copying duplicity-full-signatures.20151120T052121Z.sigtar.gpg to local cache.
    Giving up after 1 attempts. NoSuchObject: Object 'duplicity-full-signatures.20151120T052121Z.sigtar.gpg' doesn't exist (HTTP 404)

[With 0.6.24 (our server installed version), the error comes from trying to open the downloaded file rather than showing any error with the download, but I tracked it down to this.]

I'm not sure if it would cause any issues for duplicity to ignore a file that it gets in a listing but isn't there when it tries to get it, but thought I would raise this just in case something can be done (other than wait for the back up provider to work out why the listing and contents aren't in sync!).

[Kenneth Loafman (kenneth-loafman)]

duplicity was never intended to be used with unstable targets. If this index problem continues, I'd suggest another target.