Follow-up Comment #1, bug #25623 (project duplicity): I rolled back from 0.5.08 to my ubuntu Intrepid's standard 0.4.12 and now at least the error messages are potentially much more helpful:
Downloading s3+http://0ad5j1b90f3jp11nvdg2.hydra.1.backup/mnt/bind/boot/duplicity-new-signatures.2009-02-16T11:09:58-05:00.to.2009-02-16T11:13:29-05:00.sigtar.gpg gpg: encrypted with 2048-bit ELG-E key, ID 0559398E, created 2009-02-16 "Duplicity Backup (Secure) <[email protected]>" gpg: public key decryption failed: bad passphrase gpg: decryption failed: secret key not available The interesting thing is that the public key ID isn't the one I've been supplying to gpg: # gpg --list-keys /root/.gnupg/pubring.gpg ------------------------ pub 1024D/1513B6C6 2009-02-16 uid Duplicity Backup (Secure) <[email protected]> sub 2048g/0559398E 2009-02-16 I was supplying the first key ID, but duplicity says it's trying to use the 2nd one. That said, supplying the 2nd ID doesn't change anything :( _______________________________________________________ Reply to this item at: <http://savannah.nongnu.org/bugs/?25623> _______________________________________________ Message sent via/by Savannah http://savannah.nongnu.org/ _______________________________________________ Duplicity-tracker mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/duplicity-tracker
