GPG Lockfile (concurrency) issue, keyring lost: awarding 300$ for bugfix

Stefan Haller Stefan.Haller at
Wed Aug 11 14:19:33 CEST 2004


Thanks for the quick answer.

I, in fact, did use somebody else's compile. So, I checked out the HEAD 
branch from CVS now myself, but unfortunately, I cannot build it because 
of autoconf. (autoconf-2.59 from on Solaris 8).

Output is:
nhalls at parrot:~/tmp/gnupg$ autoconf error: possibly undefined macro: AM_INIT_AUTOMAKE
      If this token and others are legitimate, please use 
      See the Autoconf documentation. error: possibly undefined macro: AM_CONFIG_HEADER error: possibly undefined macro: AM_MAINTAINER_MODE error: possibly undefined macro: AM_SANITY_CHECK error: possibly undefined macro: AM_MISSING_PROG error: possibly undefined macro: AM_CONDITIONAL error: possibly undefined macro: AM_GNU_GETTEXT_VERSION error: possibly undefined macro: AM_GNU_GETTEXT

What is wrong here?

Any help apprciated.


Stefan Haller
Software Development
Transport Revenue
Ascom Autelca Ltd.
Worbstrasse 201
CH-3073 Gümligen 
+41 31 999 65 06
+41 31 999 65 82 
stefan.haller at

Simon Josefsson <jas at>
Sent by: gnupg-devel-bounces at
11/08/04 13:29

        To:     gnupg-devel at
        Subject:        Re: GPG Lockfile (concurrency) issue,   keyring lost: awarding 300$ for 

Nice idea.

Stefan Haller <Stefan.Haller at> writes:

> The patch is verified using a shell script I wrote to reproduce the 
> behaviour. It is attached to this email. The patch is only accepted if 
> script succeeds on my system. I reserve the right to adjust the test 
> script in case I built in errors into the test procedure, so just using 
> bug in the test script to make it work is not accepted... (first 100$ 
> a working patch)

Your shell script doesn't seem to have a terminating condition, except
for errors.  The $IMPORT_FINISHED file is never created, as far as I
can tell.  This is confirmed by running it, it just loops forever.
Using the development branch, I don't get any errors from the script.
Perhaps the problem is fixed in the development branch?

Did you build gpg yourself, or used someone else's build?  Perhaps
there is something wrong with the build.


Gnupg-devel mailing list
Gnupg-devel at

More information about the Gnupg-devel mailing list