GnuPG 2.1 exporting secret keys

martijn.list martijn.list at
Mon Jun 9 15:43:06 CEST 2014

On 06/09/2014 02:30 PM, martijn.list wrote:
> On 06/09/2014 11:43 AM, Werner Koch wrote:
>> On Sun,  8 Jun 2014 21:03, martijn.list at said:
>>> gpg: key 2BAD7887: asking agent for the secret parts
>>> gpg: key 2BAD7887: error receiving key from agent: Missing item in
>>> object - skipped
>> Are you sure that you are using the latest gpg-agent.
>>   gpg-connect-agent 'getinfo version' /bye
>> show the version.  Does it match the version of gpg (2.1.0-beta422)?
> Hmm strange, it reports a different version
> $ gpg-connect-agent 'getinfo version' /bye
> D 2.1.0-beta704
> I have used the following script to build it from GIT so I assumed that
> it uses the latest release from git:// since it basically
> does a "git clone git://" for all the required parts
> The script seems to clone the head and not a specific branch.

It seems that returns the wrong version.

The following command seems to return the correct version (this is from

$ git describe --match "gnupg-2.1.*[0-9]" --long


However piping it through awk (as done in it returns an
empty string

$ git describe --match "gnupg-2.1.*[0-9]" --long  | awk -F- '$3!=0 && $3
!~ /^beta/ {print"-beta"$3}'

Because of this the following line is tried:

$ git describe --match "gnupg-2.1-base" --long | awk -F-

which returns


Since this part is a recent addition to could it be that
there is a problem with the new code in relation to the current tags?

Kind regards,

Martijn Brinkers

More information about the Gnupg-users mailing list