Bug#900051: libgnupg-interface-perl: t/get_public_keys.t fails with gnupg2/2.2.7-1

[intrigeri at debian.org]

Package: libgnupg-interface-perl
Version: 0.52-9
Severity: important
X-Debbugs-Cc: dkg at debian.org

Hi!

ci.d.n alerted us about a regression in libgnupg-interface-perl test
suite since the upload of gnupg2/2.2.7-1:

  https://ci.debian.net/packages/libg/libgnupg-interface-perl/testing/amd64/
  https://ci.debian.net/data/autopkgtest/testing/amd64/libg/libgnupg-interface-perl/353934/log.gz

FWIW I've print-debugged this a bit:

  # prove -l -v t/000_setup.t t/get_public_keys.t
  t/000_setup.t ........ 
  1..1
  ok 1
  ok
  t/get_public_keys.t .. 
  1..3
  entering compare
  looking at length
  length is OK
  looking at algo_num
  algo_num is OK
  looking at hex_id
  hex_id is OK
  looking at creation_date
  creation_date is OK
  looking at creation_date_string
  creation_date_string is OK
  looking at usage_flags
  usage_flags is OK
  looking at hex_data
  hex_data is OK
  looking at expiration_date
  expiration_date is OK
  looking at expiration_date_string
  expiration_date_string is OK
  looking at fingerprint
  fingerprint is OK
  ok 1
  entering compare
  looking at length
  length is OK
  looking at algo_num
  algo_num is OK
  looking at hex_id
  hex_id is OK
  looking at creation_date
  creation_date is OK
  looking at creation_date_string
  creation_date_string is OK
  looking at usage_flags
  usage_flags is OK
  looking at hex_data
  hex_data is OK
  looking at expiration_date
  expiration_date is OK
  looking at expiration_date_string
  expiration_date_string is OK
  looking at fingerprint
  fingerprint is OK
  ok 2
  looking at user_ids
  looking at userid 0
  looking at sig 0
  looking at sig field validity
  self: !, other: !
  sig field validity is OK
  looking at sig field algo_num
  self: 17, other: 17
  sig field algo_num is OK
  looking at sig field hex_id
  self: 53AE596EF950DA9C, other: 53AE596EF950DA9C
  sig field hex_id is OK
  looking at sig field date
  self: 1177086597, other: 1177086597
  sig field date is OK
  looking at sig field date_string
  self: 2007-04-20, other: 2007-04-20
  sig field date_string is OK
  looking at sig field sig_class
  self: 19, other: 19
  sig field sig_class is OK
  looking at sig field is_exportable
  self: 1, other: 1
  sig field is_exportable is OK
  sig 0 is OK
  looking at sig 1
  looking at sig field validity
  self: !, other: ?
  sigs: 
  56FFD10A260C4FA3
  56FFD10A260C4FA3
  list user_ids item 0 does not match
  not ok 3
  Failed 1/3 subtests 
  
  Test Summary Report
  -------------------
  t/get_public_keys.t (Wstat: 0 Tests: 3 Failed: 1)
    Failed test:  3

⇒ the validity field for one of the user IDs does not match.
I don't know if that's a bug in this test case or a regression in GnuPG.

Daniel, any idea what change in GnuPG 2 (between 2.2.5-1 and 2.2.7-1)
can trigger this?

At first glance, potential candidates:

        * g10/keylist.c (list_keyblock_colon): Print a '?' for a missing key
        also in --list-mode.  Print the "issuer fpr" field also if there is an
        issuer fingerprint subpacket.

        gpg: Check that a key may do certifications.
        + commit 1a5d95e7319e7e6f0dd11064a26cbbc371b05214
        * g10/sig-check.c (check_signature_end_simple): Check key usage for
        certifications.
        (check_signature_over_key_or_uid): Request usage certification.

Worst case $someone should bisect this but I figured you might have
a hunch about what's going on here :)

Cheers,
-- 
intrigeri