Your message dated Fri, 14 Mar 2025 01:42:09 +0000 with message-id <e1tsu3t-00hhjy...@fasolo.debian.org> and subject line Bug#1088155: fixed in libgnupg-interface-perl 1.04-6 has caused the Debian Bug report #1088155, regarding libgnupg-interface-perl: FTBFS: t/get_public_keys.t (Wstat: 0 Tests: 3 Failed: 1) Failed test: 3 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.) -- 1088155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: src:libgnupg-interface-perl Version: 1.04-4 Severity: serious Tags: ftbfs trixie sid Dear maintainer: During a rebuild of all packages in unstable, your package failed to build: -------------------------------------------------------------------------------- [...] debian/rules clean dh clean dh_clean debian/rules binary dh binary dh_update_autotools_config dh_autoreconf dh_auto_configure /usr/bin/perl Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2" "LD=x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wl,-z,relro" which gpg ... /usr/bin/gpg Checking if your kit is complete... Looks good Generating a Unix-style Makefile Writing Makefile for GnuPG::Interface Writing MYMETA.yml and MYMETA.json dh_auto_build make -j1 make[1]: Entering directory '/<<PKGBUILDDIR>>' cp lib/GnuPG/PublicKey.pm blib/lib/GnuPG/PublicKey.pm cp lib/GnuPG/Interface.pm blib/lib/GnuPG/Interface.pm cp lib/GnuPG/Signature.pm blib/lib/GnuPG/Signature.pm cp lib/GnuPG/Handles.pm blib/lib/GnuPG/Handles.pm cp lib/GnuPG/Key.pm blib/lib/GnuPG/Key.pm cp lib/GnuPG/Revoker.pm blib/lib/GnuPG/Revoker.pm cp lib/GnuPG/UserAttribute.pm blib/lib/GnuPG/UserAttribute.pm cp lib/GnuPG/HashInit.pm blib/lib/GnuPG/HashInit.pm cp lib/GnuPG/PrimaryKey.pm blib/lib/GnuPG/PrimaryKey.pm cp lib/GnuPG/Fingerprint.pm blib/lib/GnuPG/Fingerprint.pm cp lib/GnuPG/UserId.pm blib/lib/GnuPG/UserId.pm cp lib/GnuPG/SubKey.pm blib/lib/GnuPG/SubKey.pm cp lib/GnuPG/SecretKey.pm blib/lib/GnuPG/SecretKey.pm cp lib/GnuPG/Options.pm blib/lib/GnuPG/Options.pm Manifying 13 pod documents make[1]: Leaving directory '/<<PKGBUILDDIR>>' debian/rules override_dh_auto_test make[1]: Entering directory '/<<PKGBUILDDIR>>' # We need to make the dummy scripts executable. chmod 755 t/bin/* # Test using gpg LC_ALL=C dh_auto_test make -j1 test TEST_VERBOSE=1 make[2]: Entering directory '/<<PKGBUILDDIR>>' PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'inc', 'blib/lib', 'blib/arch')" t/*.t gpg-connect-agent: no running gpg-agent - starting '/usr/bin/gpg-agent' gpg-connect-agent: waiting for the agent to come up ... (5s) gpg-connect-agent: connection to agent established gpg-agent[80113]: gpg-agent running and available t/000_setup.t .............. 1..1 OK ok 1 ok t/clearsign.t .............. 1..2 ok 1 ok 2 ok t/decrypt.t ................ 1..6 ok 1 ok 2 ok 3 ok 4 ok 5 ok 6 ok t/detach_sign.t ............ 1..2 ok 1 ok 2 ok t/encrypt.t ................ 1..4 ok 1 ok 2 ok 3 ok 4 ok t/encrypt_symmetrically.t .. 1..2 ok 1 ok 2 ok t/export_keys.t ............ 1..2 ok 1 ok 2 ok t/Fingerprint.t ............ 1..2 ok 1 ok 2 ok t/get_public_keys.t ........ 1..3 ok 1 ok 2 not ok 3 Failed 1/3 subtests t/get_secret_keys.t ........ 1..2 ok 1 ok 2 ok t/import_keys.t ............ 1..2 ok 1 ok 2 ok t/Interface.t .............. 1..2 ok 1 ok 2 ok t/list_public_keys.t ....... 1..3 ok 1 ok 2 ok 3 ok t/list_secret_keys.t ....... 1..4 ok 1 ok 2 ok 3 ok 4 ok t/list_sigs.t .............. 1..3 ok 1 ok 2 ok 3 ok gpg: using "0x93AFC4B1B0288A104996B44253AE596EF950DA9C" as default secret key for signing t/passphrase_handling.t .... 1..3 ok 1 ok 2 ok 3 ok t/sign.t ................... 1..2 ok 1 ok 2 ok t/sign_and_encrypt.t ....... 1..2 ok 1 ok 2 ok t/taint_mode.t ............. 1..2 ok 1 ok 2 ok t/update_version.t ......... 1..2 ok 1 ok 2 ok t/UserId.t ................. 1..2 ok 1 ok 2 ok t/verify.t ................. 1..2 ok 1 ok 2 ok t/version_updates.t ........ 1..3 ok 1 ok 2 ok 3 ok t/wrap_call.t .............. 1..4 ok 1 ok 2 ok 3 ok 4 ok t/z_delete_keys.t .......... 1..3 ok 1 ok 2 ok 3 ok t/zzz_cleanup.t ............ 1..1 ok 1 ok Test Summary Report ------------------- t/get_public_keys.t (Wstat: 0 Tests: 3 Failed: 1) Failed test: 3 Files=26, Tests=66, 13 wallclock secs ( 0.04 usr 0.03 sys + 3.74 cusr 1.29 csys = 5.10 CPU) Result: FAIL Failed 1/26 test programs. 1/66 subtests failed. make[2]: *** [Makefile:809: test_dynamic] Error 255 make[2]: Leaving directory '/<<PKGBUILDDIR>>' dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned exit code 2 make[1]: *** [debian/rules:10: override_dh_auto_test] Error 25 make[1]: Leaving directory '/<<PKGBUILDDIR>>' make: *** [debian/rules:4: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 -------------------------------------------------------------------------------- The above is just how the build ends and not necessarily the most relevant part. If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202503/ About the archive rebuild: The build was made on virtual machines from AWS, using sbuild and a reduced chroot with only build-essential packages. If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and add an affects on src:libgnupg-interface-perl, so that this is still visible in the BTS web page for this package. Thanks.
--- End Message ---
--- Begin Message ---Source: libgnupg-interface-perl Source-Version: 1.04-6 Done: gregor herrmann <gre...@debian.org> 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 1088...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann <gre...@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: SHA512 Format: 1.8 Date: Fri, 14 Mar 2025 01:52:17 +0100 Source: libgnupg-interface-perl Architecture: source Version: 1.04-6 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group <pkg-perl-maintain...@lists.alioth.debian.org> Changed-By: gregor herrmann <gre...@debian.org> Closes: 1088155 Changes: libgnupg-interface-perl (1.04-6) unstable; urgency=medium . * Team upload. . [ Daniel Kahn Gillmor ] * note forwarding flexible validity marker upstream . [ gregor herrmann ] * Update years of packaging copyright. * Declare compliance with Debian Policy 4.7.2. * Add bug closer to 1.04-5 changelog entry. . libgnupg-interface-perl (1.04-5) unstable; urgency=medium . [ gregor herrmann ] * Update debian/upstream/metadata to use Github for bugs. . [ Daniel Kahn Gillmor ] * Add e-mail addresses to patch authorship fields * Clarify comment in patch * Accept variant reports of validity for expired signatures on 2.2 (see #1100074 and https://dev.gnupg.org/T7547) Closes: #1088155 * Further cleanup of test suite, including fixes for 2.4 Checksums-Sha1: 6ec5cde9c23ab8722a9bd29bc1b9d438e1d2c8cc 2723 libgnupg-interface-perl_1.04-6.dsc c5ca61206117d0dac4539d24bc4f01cc8e847adf 12704 libgnupg-interface-perl_1.04-6.debian.tar.xz Checksums-Sha256: 9148db7f0e9a993e7c91d65895dd6ca4c323b5c71938768fb0ae85e1202b75ae 2723 libgnupg-interface-perl_1.04-6.dsc dc5ad75d732c2cddc0162832b884dfede1874d979a93d10dd9c06d69b5bde302 12704 libgnupg-interface-perl_1.04-6.debian.tar.xz Files: d3eeea611a5f92565486b19b5bd3f889 2723 perl optional libgnupg-interface-perl_1.04-6.dsc 69262b54d0c4f8af757641130ccf9dd9 12704 perl optional libgnupg-interface-perl_1.04-6.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmfTftRfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgaP3A//crw8MhdUy5o/tMs8ZtKS+3Uz8JgqlLNcWcdEgZhZ2sFEZHv+WcVv/Du4 Tw2ZDMb+lKVXAhAfDptvoMb2FFWrRYaXW/My9Fta/102miprCj3XFJaok6g7FPAZ R3CNMeiEzzfuNJLGsVHXVDjCQWe2DhF7jww+l4w0E5BlK6n03zvt8Ejfpy1nuic7 RDDa11KnJxNZ/Ub/l/kBMrYEW4FkjdiWA/p5zcDwAkKDpYkJMVrSt3+7Boq5gmx5 v/PlUA+1P//Y367TJvxpX2sMMnpbbRh8Zl+91sUSdV/h5ecZnCqB1byKJ8hlPasJ ZsvsO7hHWSn8onFRsniRI8XaBKvqe82NI2KZ9oXF4Y+5hKyTia8LiqMBpZ/XV5Cs HCAKpXoIfGYCN2zlMVn2SiAmFxoeFJ4BLXRb8CBSjZToIqXplF7vlswYmcROobnq XIdY+8xab+HmHlWHNCMQgykpVB/6uoXmiS2oHi8SdmIKVvawT/PvsGe3NZqGSPZC VI31fHPvAS+YFZDtWlCCjIiUze5/+0O56GMl2KkGfW5pexqMkodD+0pVvoJ38IrL CeNqCKEGSh/AnUjhrCC5F73lS85CAeNzDmtyuI9JLYkHsGXOqkfxp5TNPRyroqZ2 G0HEIchg1SMs+mlRajdrW8MNKL6KVbfZ2+O9K3tDOK61BHJJZkY= =iD0E -----END PGP SIGNATURE-----
pgp_kpo04b0Fv.pgp
Description: PGP signature
--- End Message ---
