test/crypto: hard code fingerprint

Originally the intent was to make the test more robust against changing
test keys. It turns out that (unscientifically) gpg --with-colons output
changes more often than our test key. Rather than making the script more
complex, just hard code the fingerprint.

This fixes Debian bug #847013; I expect similar test failures as other
distros adopt gnupg 2.1.15
This commit is contained in:
David Bremner 2016-09-08 09:03:15 -03:00
parent 98da3c079a
commit 7edded2740

View file

@ -25,8 +25,8 @@ add_gnupg_home ()
################################################## ##################################################
add_gnupg_home add_gnupg_home
# get key fingerprint # Change this if we ship a new test key
FINGERPRINT=$(gpg --no-tty --list-secret-keys --with-colons --fingerprint | grep '^fpr:' | cut -d: -f10) FINGERPRINT="5AEAB11F5E33DCE875DDB75B6D92612D94E46381"
test_expect_success 'emacs delivery of signed message' \ test_expect_success 'emacs delivery of signed message' \
'emacs_fcc_message \ 'emacs_fcc_message \