Question #183711 on Duplicity changed: https://answers.launchpad.net/duplicity/+question/183711
Status: Open => Answered rax proposed the following answer: Chris, Douglas, I'm having unrelated but similar issues in just getting duplicity to play with gpg-agent. I'm just a newbie so I might not be able to add much - or you may know a lot more than me, in which case just ignore this. >From what I've been able to deduce, it's not enough to have gpg-agent running. The passphrase needs to be loaded into the cache in order for gpg-agent to actually have the passphrase available. Since you had a long backup, after the backup broke, the passphrase might have timed out of the cache. Try the following to get the passphrase into the cache (I'm assuming this is an encryption key and not a signing key - although you don't need to use the former to encrypt, duplicity might need it to decrypt the archive to see where it got up to with an interrupted backup - I'm guessing); $ touch dummy.in $ gpg --output dummy.asc --encrypt dummy.in Give your backup encryption key ID when prompted. Once the encryption process is complete, decrypt. $ gpg --output dummy.out --decrypt dummy.asc You will now be prompted for your encryption passphrase. It is this process which should load the passphrase back into the cache. Now try your backup again. -- 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