Comment 3 for bug 1266753

In the trunk. You can get it with: bzr branch lp:duplicity

On Mon, Jan 13, 2014 at 8:26 AM, Kurt Huwig <email address hidden> wrote:

> "Fix Committed"? Where can I find the fix?
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/1266753
>
> Title:
> Boto backend removes local cache if connection cannot be made
>
> Status in Duplicity - Bandwidth Efficient Encrypted Backup:
> Fix Committed
>
> Bug description:
> When there is no connection to the S3 backend, the local cache files
> are deleted. To reproduce:
>
> 1. disable the connection to S3
> 2. run a "collection-status" (basically I run 'duply X status')
>
> You'll get a bunch of these:
>
> Deleting local
> /srv/duply-cache/duply_srv/duplicity-inc.20140106T010002Z.to.20140107T010002Z.manifest
> (not authoritative at backend).
> Deleting local
> /srv/duply-cache/duply_srv/duplicity-new-signatures.20131211T124323Z.to.20131211T124519Z.sigtar.gz
> (not authoritative at backend).
>
> This is fatal if you run it in a configuration using GPG and having
> only the public key for encryption as well as a separate signing key.
> Then you cannot backup any more, as the decrypted local cache has been
> deleted and the files on the S3 are encrypted.
>
> Probably reason:
>
> There is no check if the connection to the backend could be
> established
>
> Workaround:
>
> If you replace at
>
> http://bazaar.launchpad.net/~duplicity-
>
> team/duplicity/0.6-series/view/head:/duplicity/backends/_boto_single.py#L270
>
> the line
>
> return []
>
> with
>
> return None
>
> Then duplicity will crash instead of deleting the local files. Not the
> proper solution but at least you can do a backup when the connection
> comes back up.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/duplicity/+bug/1266753/+subscriptions
>