[Duplicity-talk] Why is passphrase required to write backups?

[James Utter]

Hi, this is my first post to this list.

Running the following command is failing for me:

~$ duplicity --encrypt-key 82C98841 /home/james file:///tmp/backup-23-10-07
GnuPG passphrase:
Retype to confirm:
No signatures found, switching to full backup.
Traceback (most recent call last):
  File "/usr/bin/duplicity", line 394, in ?
    if __name__ == "__main__": main()
  File "/usr/bin/duplicity", line 387, in main
    if not sig_chain: full_backup(col_stats)
  File "/usr/bin/duplicity", line 146, in full_backup
    bytes_written = write_multivol("full", tarblock_iter, globals.backend)
  File "/usr/bin/duplicity", line 82, in write_multivol
    globals.gpg_profile,globals.volsize)
  File "/usr/lib/python2.4/site-packages/duplicity/gpg.py", line 202,
in GPGWriteFile
    file.write(data)
  File "/usr/lib/python2.4/site-packages/duplicity/gpg.py", line 117, in write
    def write(self, buf): return self.gpg_input.write(buf)
IOError: [Errno 32] Broken pipe
close failed: [Errno 32] Broken pipe


Also, why do I need to type the passphrase (and twice!) when using
public key encryption? Surely I should only have to type the key when
restoring from a backup, or if I was using a sign-key.

Cheers,

James