diff options
| author | Jeff King <peff@peff.net> | 2015-01-29 18:43:20 +0300 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2015-01-29 22:56:19 +0300 |
| commit | 830ff021aaaf12c43f06314feaf465377672d3ea (patch) | |
| tree | fad830565e8f186577a29b84a06d8eaf03f0e934 /t/lib-gpg.sh | |
| parent | 6fb5df6c77070f7cea5391572003ecfea3235650 (diff) | |
t/lib-gpg: include separate public keys in keyring.gpg
Since 1e3eefb (tests: replace binary GPG keyrings with
ASCII-armored keys, 2014-12-12), we import our test GPG keys
from a single file. Each keypair in the import stream
contains both the secret and public keys. However, older
versions of gpg reportedly fail to import the public half of
the key. We can solve this by including duplicates of the
public keys separately. The duplicates are ignored by modern
gpg, and this makes older versions work.
Reported by Tom G. Christensen <tgc@statsbiblioteket.dk> on
gpg 1.2.6 (from RHEL4).
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/lib-gpg.sh')
| -rwxr-xr-x | t/lib-gpg.sh | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/t/lib-gpg.sh b/t/lib-gpg.sh index d88da29f77..16e0d3fcaf 100755 --- a/t/lib-gpg.sh +++ b/t/lib-gpg.sh @@ -23,6 +23,8 @@ else # To write armored exported key to keyring: # gpg --homedir /tmp/gpghome --export-secret-keys \ # --armor 0xDEADBEEF >> lib-gpg/keyring.gpg + # gpg --homedir /tmp/gpghome --export \ + # --armor 0xDEADBEEF >> lib-gpg/keyring.gpg # To export ownertrust: # gpg --homedir /tmp/gpghome --export-ownertrust \ # > lib-gpg/ownertrust |