Can't use GPG key - secret key not available

[Madhusudan Singh]

I had given up on this last year but want to make the key signing work
again.

I still have the same error:

GPG error detail: Traceback (most recent call last):
  File "/opt/local/bin/duplicity", line 1245, in <module>
    with_tempdir(main)
  File "/opt/local/bin/duplicity", line 1238, in with_tempdir
    fn()
  File "/opt/local/bin/duplicity", line 1211, in main
    full_backup(col_stats)
  File "/opt/local/bin/duplicity", line 417, in full_backup
    globals.backend)
  File "/opt/local/bin/duplicity", line 295, in write_multivol
    globals.gpg_profile, globals.volsize)
  File
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/duplicity/gpg.py",
line 283, in GPGWriteFile
    file.write(data)
  File
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/duplicity/gpg.py",
line 153, in write
    self.gpg_failed()
  File
"/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/duplicity/gpg.py",
line 165, in gpg_failed
    raise GPGError, msg
GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: no default secret key: secret key not available
gpg: [stdin]: sign+encrypt failed: secret key not available
===== End GnuPG log =====


GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: no default secret key: secret key not available
gpg: [stdin]: sign+encrypt failed: secret key not available
===== End GnuPG log =====

Any ideas?

On Fri, Oct 1, 2010 at 5:01 PM, Charly Avital <shavital at mac.com> wrote:

> Madhusudan Singh wrote the following on 10/1/10 2:35 PM:
> > Tried this.
> >
> > No use.
> >
> > I have two keys installed on this machine (different email addresses).
> > It just can't seem to use the newer one, regardless of the default-key
> > parameter.
> >
> > Do I have to restart start-gpg-agent on Mac ? If so, how do I restart
> > without rebooting ?
>
> I am not familiar with duplicity backup to S3.
>
> I don't know whether restarting gpg-agent will help (without rebooting),
> but try this.
>
> Locate start-gpg-agent.app (it is, in fact, an application) and double
> click on it.
>
> Another factor comes to mind. Have you signed your "new" key with the
> "old" one? It is just possible (I am speculating) that the systems does
> not recognize your new key because it has not been authenticated with
> your default key.
>
> Best regards,
> Charly
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20110104/1291759c/attachment.htm>