Your message dated Fri, 29 Jun 2018 08:49:14 +0000
with message-id <e1fyp5e-0003bg...@fasolo.debian.org>
and subject line Bug#900051: fixed in libgnupg-interface-perl 0.52-10
has caused the Debian Bug report #900051,
regarding libgnupg-interface-perl: t/get_public_keys.t fails with gnupg2/2.2.7-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
900051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgnupg-interface-perl
Version: 0.52-9
Severity: important
X-Debbugs-Cc: d...@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

--- End Message ---
--- Begin Message ---
Source: libgnupg-interface-perl
Source-Version: 0.52-10

We believe that the bug you reported is fixed in the latest version of
libgnupg-interface-perl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 900...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Niko Tyni <nt...@debian.org> (supplier of updated libgnupg-interface-perl 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 29 Jun 2018 11:20:20 +0300
Source: libgnupg-interface-perl
Binary: libgnupg-interface-perl
Architecture: source
Version: 0.52-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group <pkg-perl-maintain...@lists.alioth.debian.org>
Changed-By: Niko Tyni <nt...@debian.org>
Description:
 libgnupg-interface-perl - Perl interface to GnuPG
Closes: 900051
Changes:
 libgnupg-interface-perl (0.52-10) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-* headers for switch to salsa.debian.org
 .
   [ Niko Tyni ]
   * Patch the test suite for GnuPG >= 2.2.8 compatibility.
     (Closes: #900051)
   * Update to debhelper compat level 10
   * Update to Standards-Version 4.1.4
   * Declare that the package does not need (fake)root to build
Checksums-Sha1:
 65ede612c4fc77051efd454d48f378810c246e44 2353 
libgnupg-interface-perl_0.52-10.dsc
 ba01c144624358e3e602126bcfc7a489741b4e6e 23360 
libgnupg-interface-perl_0.52-10.debian.tar.xz
 47a32960f010ef7b18cb133d1301067ba652ddac 5913 
libgnupg-interface-perl_0.52-10_source.buildinfo
Checksums-Sha256:
 43738e6dce2937882523876e3c2fbddea28179f8c4f06e77d817032c274d6238 2353 
libgnupg-interface-perl_0.52-10.dsc
 69d6183f6f75fd3fb376452b39ce8f095cb7525926085f48a4bdd696543ea245 23360 
libgnupg-interface-perl_0.52-10.debian.tar.xz
 1723844db0a74a34875d11b47126a8ffab92969d264209f4347fe3abfd969dfb 5913 
libgnupg-interface-perl_0.52-10_source.buildinfo
Files:
 54b43966ae2ac8bd94f2eef35cb1c8df 2353 perl optional 
libgnupg-interface-perl_0.52-10.dsc
 7dfcd41921452823d201dacd247c448b 23360 perl optional 
libgnupg-interface-perl_0.52-10.debian.tar.xz
 4bb62b6f4b9ad5393023ea12c1181d68 5913 perl optional 
libgnupg-interface-perl_0.52-10_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEdqKOQsmBHZHoj7peLsD/s7cwGx8FAls17LcACgkQLsD/s7cw
Gx/Y4g/+IsGuJoXazKF+y9DfExmt3DPV5a17rgUuDfgwm0ifZyqfi+NMSOErgjFH
TK31v6uLsFalslCsdwx2Aj4oZdow56cvoqzxWGwvj65RbCKyT/GchyOi9JYfVyjP
An8dY/2nPhnImbjShPDW/6znsktPebo37bbXK4syhlGMBgS7f6gprAfTcwFBhQHT
5cuJOxS3mtd+HnvXpKmC6MXYq7kC1Sd8Vy2VDBezbjzMz4V9Kco6xtrd0F1VxMUJ
wBBzWmSqMSeMGuRJPQmVHuBNv1OonCgDLC+TciCj/LWtY6Y1Y+Hvc835C+xXDgFC
Bc6a51oOwLn939jyHO/79Hp5HM7HxkxDRGKVKpq3/ny8SR0n7+BhKVcPctFdtUvA
AXhafVfcPRFaa0FdWZp8hm1uzOOd4RZoruxIXfz056vZ6Y/GcVg3Ll872QJxMsyT
mHQRCO8kmXa2C+2+uxJRvs82hTmyUmgt/DzfttUKqBWVp+1A6xVjOtTbrwFcr/EI
Qp3goBoB04GjrUt7GMuKD+ByzcxxQZdEq3FflMntGOKJPoEpHvcDugyxBbJGKhRt
0bsLijI1IE0Iiid27UWTowTKLsVICxSWC42dXWcnqepnFvgYuDsZNgFEJjjb36fT
FYUyqjpqP/5m4tDu5K0gIUFvwKABG+qTfI9vEIZMjuK/4zBVbqU=
=Wpk9
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to