[pkg-gnupg-maint] Bug#889594: dgit started to fails its autopkgtests, with git gnupg2/2.2.4-1+

[Ian Jackson]

Control: reassign -1 gnupg2
Control: found -1 2.2.4-1

Dimitri John Ledkov writes ("Bug#889594: dgit started to fails its autopkgtests, with git gnupg2/2.2.4-1+"):
> dgit used to pass its autopkgtests, but doesn't anymore.
...
> Note, this appears to be due to a change in gnupg2 package.

gnupg2's agent startup code is full of races.  Probably, the new
gnupg2 has more races, or worse races, or happens to trigger the
existing races more of the time.

For more information see
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868550

> I am currently trying to upgrade gnupg2 package in Ubuntu, and this
> autopkgtest failure is preventing me from doing so.

I'm afraid that the bug is in gnupg2, not in dgit or its test suite.

> I am not familiar with the dgit internals, but there appear to be a
> lot of warnings from gnupg w.r.t.
> unsave homedir permissions

The unsafe homedir permissions are expected and intentional; the dgit
test suite uses a special set of keys, including private keys
distributed in the dgit source code.  So the GNUPGHOME set by the dgit
test suite has permissions which would normally be unsafe for gpg but
are fine in this context.

> and lack of secret keys.

The "missing secret key" message from gnupg2 is a bad error message.
What it means is that it has fumbled its agent startup and is unable
to access any secret keys at all.

> Possibly the dgit test-suite is not using gnupg-agent,
> as it is now required by gnupg.

"Required" ?  AIUI gnupg2 is supposed to start its own agent on
demand.

> Would you please be able to look into upgrading/fixing dgit
> autopkgtests?

Maybe I should change the dgit test suite to automatically retry
failing tests when run under autopkgtest, as well as when run ad-hoc
by hand.

See
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868550#85

Ian.