Question #140813 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/140813
Status: Open => Answered
edso proposed the following answer:
the real problem:
duplicity _needs_ the secret key. even 0.6.11 ... we are planning to
remove this necessity, but until then provide one.
i'd guess that duplicity only sees a difference, because of the before
mentioned problem, and tries to synchronize the archive dir failing doing so
because of the impossibility to decrypt.
i'd be interested what happens if you to solve the problem for now, just
provide the secret key, which files get update/deleted. you can remove it after
you applied teh following 'solution'.
you can encrypt with several keys by using multiple encrypt-key parameters so
you won't have to place your personal secret key on that machine.
read more here: https://bugs.launchpad.net/duplicity/+bug/687295
regards ede
--
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.
_______________________________________________
Mailing list: https://launchpad.net/~duplicity-team
Post to : duplicity-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~duplicity-team
More help : https://help.launchpad.net/ListHelp
