[Rt-commit] rt branch, 5.0/support-gpg-2.2, repushed
? sunnavy
sunnavy at bestpractical.com
Fri May 15 20:37:51 EDT 2020
The branch 5.0/support-gpg-2.2 was deleted and repushed:
was b69522d284beaa3947dbac9fd801f8e1d45e325d
now 42488ef0061d96da027e5eb9dcb5bdba940da743
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 < --: ------- Add gpg.conf for gpg 2.2 so we can specify passphrase in command line
--: ------- > 5: d7db6faad8 Add gpg.conf for gpg 2.2 so we can specify passphrase in command line
6: 09201a7592 = 6: 3722d4c205 Update warning message tests for gpg 2.2
7: 0547b8ff05 = 7: 147ebd0beb Don't override fingerprint if it exsits already
8: d55a6ae8e4 ! 8: 0063439530 Make t/mail/crypt-gnupg.t happy with gpg 2.2
@@ -17,7 +17,7 @@
+use RT::Test::GnuPG tests => undef, gnupg_options => { homedir => $homedir, quiet => 1 };
use Test::Warn;
-+my ($gnupg_version) = split /\./, GnuPG::Interface->new->version;
++my $gnupg_version = RT::Test::GnuPG::gnupg_version;
+
use_ok('RT::Crypt');
use_ok('MIME::Entity');
9: b69522d284 ! 9: 77ed189c47 Bump GnuPG::Interface to 1.00 to support gpg 2.2
@@ -14,3 +14,4 @@
requires 'PerlIO::eol';
};
+
--: ------- > 10: e8d43332fa Quit gpg-agent after tests for gpg 2.2
--: ------- > 11: 194b1ac55b Move signed_old_style_with_attachment.eml to emails directory where it belongs to
--: ------- > 12: 42488ef006 Always use temp gpg homedir to get a cleaner env
More information about the rt-commit
mailing list