Merge lp:~xnox/britney/badtest-dgit-unlock-gnupg2 into lp:~ubuntu-release/britney/hints-ubuntu

[Dimitri John Ledkov]

unlock gnupg2

[Steve Langasek (vorlon)]

Per the comments on the Debian bug from the dgit maintainer, there is not consensus that this is a bug in dgit rather than in gnupg2; also, it's unclear from the discussion so far that this issue only impacts the test suite.

Without further information, this does not look appropriate to override.

review: Needs Information

[Dimitri John Ledkov (xnox)]

The dgit test-suite does expose race conditions in gnupg2, which were previously present as well, but have become loosing a lot more often. This by itself, does not indicate a failur of gnupg2, as that would normally have a gnupg-agent socket activated and managed by user session systemd. This also does not indicate a failure in dgit, it only shows the excellence of its test-suite to excercise races.

However, it is more important to ship an up to date gnupg2 implementation to our users, then to block on a developer-only tool's testsuite improvements.

The race condition exposed, is being discussed in the upstream bug tracker.

[Steve Langasek (vorlon)]

review: Approve

=== modified file 'vorlon'
--- vorlon	2018-02-04 18:11:47 +0000
+++ vorlon	2018-02-04 21:06:07 +0000
@@ -246,3 +246,7 @@
 
 # sil2100: started failing in bionic, ruby2.3 will go away anyway soon
 force-badtest ruby2.3/2.3.6-2/arm64
+
+# xnox: dgit fails its ADT tests with new gnupg2, filed https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889594.
+# this is blocking gnupg2 migration...
+force-badtest dgit/4.3