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.l...@gmail.com 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://git.gnupg.org since it basically
> does a "git clone git://git.gnupg.org" for all the required parts
>
> https://github.com/Wikinaut/utils/wiki#How_to_compile_GnuPG_gpg_from_the_github_sources
>
> The script seems to clone the head and not a specific branch.
It seems that autogen.sh returns the wrong version.
The following command seems to return the correct version (this is from
autogen,sh)
$ git describe --match "gnupg-2.1.*[0-9]" --long
gnupg-2.1.0-beta442-2-gb67e4e5
However piping it through awk (as done in autogen.sh) 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-
'$4!=0{print"-beta"$4}'
which returns
-beta704
Since this part is a recent addition to autogen.sh could it be that
there is a problem with the new code in relation to the current tags?
Kind regards,
Martijn Brinkers
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
