GPG Lockfile (concurrency) issue,
keyring lost: awarding 300$ for bugfix
Stefan.Haller at ascom.ch
Fri Aug 13 09:38:44 CEST 2004
The latest development version as indicated by Simon Josefsson did not
work for me. And in fact, my test script was buggy of course, I include
the latest in this email again.
Werner, your patch works great for me. I'm especially happy with the fact
that I do not need to consider the lock-exit code thanks to your 10 second
I have only two questions, is there a good reason that I get the following
gpg: some signal caught ... exiting
I got this message 20 times during the period that is required to import
50 keys... But exit code seems to be 0 always and I cannot spot any real
problem with it.
Second question, are you going to include this patch in the development
branch that is used for the next stable release?
I will contact you, Werner, directly for payment details...
Thanks for the quick help!
Ascom Autelca Ltd.
+41 31 999 65 06
+41 31 999 65 82
stefan.haller at ascom.ch
Werner Koch <wk at gnupg.org>
Sent by: gnupg-devel-bounces at gnupg.org
To: gnupg-devel at gnupg.org
Subject: Re: GPG Lockfile (concurrency) issue, keyring lost: awarding 300$ for
On Wed, 11 Aug 2004 13:08:36 +0200, Stefan Haller said:
> I upgraded to 1.2.5, but the issues are still present. I looked at the
> code myself, but I think it will require a lot of time for me to fix the
Please apply the attached patch against 1.2.5 and see whether it works for
I could verify it using your script.
Gnupg-devel mailing list
Gnupg-devel at gnupg.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 10856 bytes
Desc: not available
Url : /pipermail/attachments/20040813/d96854cb/apatch.exe
More information about the Gnupg-devel