NIIBE Yutaka writes ("Re: [pkg-gnupg-maint] Bug#868550: reprepro seems to
provide a repro"):
> Ian Jackson <ijack...@chiark.greenend.org.uk> wrote:
> > gpg --ignore-time-conflict
> > --no-options
> > --no-default-keyring
> > --homedir
> > /tmp/apt-key-gpghome.yLlu1bwwPI
> > --no-auto-check-trustdb
> > --trust-model
> > always
> > --batch
> > --import
>
> Thank you for minimizing. I'd like to clarify the case. Is this
> importing private key?
I think so, but I'm not sure.
> The invocation of gpg-agent by gpg frontend has an inherent race in the
> current implementation; When gpg frontend invokes gpg-agent, after
> spawning gpg-agent, gpg frontend tries to connect five times with one
> second intervals. When a machine is busy enough and scheduling of
> processes goes not that fair, the connection to gpg-agent from gpg
> frontend may fail.
This might be relevant. My test suite failures occur on a loaded
machine, because the test case runner parallelises separate tests.
Does this produce a particular message, when it occurs ?
There are other possible approaches to this situation than to hope to
win the race. But I hesitate to suggest adding additional code to
this area, having seen what's there already...
If you would like to suggest a debug printf, or name lines of source
code, I can probably arrange to see if this is happening.
Ian.
