[Rt-commit] rt branch, 5.0/support-gpg-2.2, repushed

? sunnavy sunnavy at bestpractical.com
Fri May 15 17:19:30 EDT 2020


The branch 5.0/support-gpg-2.2 was deleted and repushed:
       was 549b99820767151c3f1dda1f9bc6750d7d3c8c99
       now b69522d284beaa3947dbac9fd801f8e1d45e325d

1: 734bc6972f = 1: 734bc6972f Fix uninitialized warnings of $latest_user_main_key for gpg 2.2
2: 4cc1b76b74 = 2: 4cc1b76b74 Handle FAILURE keyword for gpg 2.2
3: ee9a2a7bcf = 3: ee9a2a7bcf Add extra ignored keywords for gnupg 2.2.x
4: 37eb1901a6 = 4: 37eb1901a6 Default cert-digest-algo from SHA1 to SHA256
5: 58580e0569 = 5: 58580e0569 Add gpg.conf for gpg 2.2 so we can specify passphrase in command line
6: 09201a7592 = 6: 09201a7592 Update warning message tests for gpg 2.2
7: 0547b8ff05 = 7: 0547b8ff05 Don't override fingerprint if it exsits already
8: 113fab11d6 ! 8: d55a6ae8e4 Make t/mail/crypt-gnupg.t happy with gpg 2.2
    @@ -61,7 +61,7 @@
      diag 'only signing. missing passphrase';
     -{
     +SKIP: {
    -+    skip "gpg-agent caches passphrase", 6 unless $gnupg_version < 2;
    ++    skip "Test hangs waiting for passphrase", 6 unless $gnupg_version < 2;
          my $entity = MIME::Entity->build(
              From    => 'rt at example.com',
              Subject => 'test',
9: 549b998207 = 9: b69522d284 Bump GnuPG::Interface to 1.00 to support gpg 2.2



More information about the rt-commit mailing list