Re: master 26f9a77: * etc/package-keyring.gpg: Add the 2019 key

[Robert Pluim]

>>>>> On Fri, 26 Apr 2019 16:17:22 +0200, Robert Pluim <address@hidden> said:

    Robert> - I was expecting .emacs.d/elpa/gnupg/pubring.gpg to
    Robert> change, but it hasn't changed in size, nor has its
    Robert> timestamp. pubring.kbx *has* changed however

One more data point, if I re-run the import, then gpg indicates the
new key is already there:

/usr/local/bin/gpg2 --no-tty --status-fd 1 --yes --homedir 
/Users/rpluim/.emacs.d/elpa/gnupg --command-fd 0 --import -- 
/Users/rpluim/.emacs.d/elpa/gnu-elpa-keyring-update-2019.1/etc/gnu-elpa-keyring.gpg
[GNUPG:] IMPORT_OK 0 CA442C00F91774F17F59D9B0474F05837FBDEF9B
[GNUPG:] KEY_CONSIDERED CA442C00F91774F17F59D9B0474F05837FBDEF9B 0
gpg: key 474F05837FBDEF9B: "GNU ELPA Signing Agent (2014) <address@hidden>" not 
changed
[GNUPG:] KEY_CONSIDERED CA442C00F91774F17F59D9B0474F05837FBDEF9B 0
[GNUPG:] IMPORT_OK 0 C433554766D3DDC64221BFAA066DAFCB81E42C40
[GNUPG:] KEY_CONSIDERED C433554766D3DDC64221BFAA066DAFCB81E42C40 0
gpg: key 066DAFCB81E42C40: "GNU ELPA Signing Agent (2019) <address@hidden>" not 
changed
gpg: Total number processed: 2
gpg:              unchanged: 2
[GNUPG:] IMPORT_RES 2 0 0 0 2 0 0 0 0 0 0 0 0 0 0

So I think that checking pubring.gpg is perhaps the wrong thing to do
when using gpg2, which is supported by the 'Faster Keyring Format'
section of <https://gnupg.org/faq/whats-new-in-2.1.html>

Robert