duplicity-team team mailing list archive

[Mark Haylock <question140813@xxxxxxxxxxxxxxxxxxxxx>]

New question #140813 on Duplicity:
https://answers.launchpad.net/duplicity/+question/140813

Hi,

I'm having a bit of trouble, after I ran the following command:

duplicity remove-older-than 30D --force scp://username@server/path/to/files

It appeared to complete ok, with exception being that it outputted this warning:

Warning, found the following local orphaned signature files:
duplicity-new-signatures.20101207T092449Z.to.20101207T121233Z.sigtar.gz
(lots of lines like this)

I would like to know how to remove that message, however the real problem I'm having is that after running this I get the following error message when running any duplicity command (cleanup here, but it happens for a backup too):

duplicity cleanup scp://username@server/path/to/files
Synchronizing remote metadata to local cache...
Copying duplicity-full-signatures.20101030T130733Z.sigtar to local cache.
GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: encrypted with 2048-bit ELG-E key, ID AEC02631, created 2010-10-07
"Encryption Key"
gpg: decryption failed: secret key not available
===== End GnuPG log =====

Based on this message it appears that the remove-older-than deleted cache files it shouldn't have and so it tried to update from the remote, but then it wants to decrypt the remote signatures? How can I fix this? I want this to run automated and don't want to provide the private key for the encryption key in any script as that is not secure.

I have replicated this behavior on all 3 machines that I am running duplicity on, so it's either a bug in duplicity or a problem with my setup?

Note that this is with duplicity 0.6.10, I don't have time today to upgrade to 0.6.11, but let me know if this should help.

Thank you for any help you can provide.

-- 
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.