gpa fails to deal with my key: Invalid crypto engine

[Jim Meyering]

Werner Koch wrote:
> just a few quick comments for now:
>
> On Sat,  3 Sep 2011 10:26, jim at meyering.net said:
>
>>     gpg --keyring test --import \
>>       <(wget -O - http://meyering.net/key/000BEEEE.gpg)
>
>   gpg --keyring test --fetch-key http://meyering.net/key/000BEEEE.gpg
>
> is easier ;-)

And more portable ;-)
Thanks!

>>     src/gpa --keyring=test
>
> GPA does not support --keyring with a value.  --keyring merely means to
> start with the key manager.
>
>>     The GPGME library returned an unexpected
>>     error. The error was:
>
> To debug this you may do
>
>   GPGME_DEBUG=9:/foo/gpgme.log src/gpa --keyring
>
> watch out for gpg started with --version.

Thanks.
It reports gpg2, which is gnupg2-2.0.17-1.fc15.x86_64

Here's a reproducer that imports into an empty $HOME and .gnupg directory:

    #!/bin/sh
    d=$(mktemp -d)
    echo $d
    mkdir -p $d/.gnupg
    export HOME=$d

    gpg --fetch-key http://meyering.net/key/000BEEEE.gpg

    # Or wherever you have gpa cloned
    GPGME_DEBUG=9:/foo/gpgme.log ~/w/gpa/src/gpa

Here's the full log:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: gpgme.log.gz
Type: application/octet-stream
Size: 15099 bytes
Desc: not available
URL: </pipermail/attachments/20110904/28e1dc8a/attachment-0001.obj>