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

[Robert Pluim <rpluim@gmail.com>]

>>>>> On Fri, 26 Apr 2019 07:57:54 -0400, Stefan Monnier <monnier@IRO.UMontreal.CA> said:

    Stefan> Sounds like a bug: the import should have taken place
    Stefan> during the installation (more specifically during the
    Stefan> compilation) of gnu-elpa-keyring-update and it should not
    Stefan> need to be performed "ever again".  And if for some reason
    Stefan> it didn't happen during installation, it should happen at
    Stefan> the next startup but not at the subsequent ones.

    Stefan> So could you try and figure out why it happens every time
    Stefan> you start Emacs?

There is a bug somewhere, but itʼs not clear where:

- when I installed gnu-elpa-keyring-update, I was prompted for a gpg key
to use to encrypt. I chose one, which meant that
gnu-elpa-keyring-update-2019.1/etc/gnu-elpa-keyring.gpg
ended up encrypted, and gpg could not import it.

- I manually decrypted gnu-elpa-keyring.gpg, and relaunched emacs.

- This time, epg debug shows that gpg imported something:

GPG_AGENT_INFO is not set
/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
[GNUPG:] KEY_CONSIDERED CA442C00F91774F17F59D9B0474F05837FBDEF9B 0
[GNUPG:] IMPORT_OK 0 C433554766D3DDC64221BFAA066DAFCB81E42C40
[GNUPG:] KEY_CONSIDERED C433554766D3DDC64221BFAA066DAFCB81E42C40 0
[GNUPG:] IMPORT_RES 2 0 0 0 2 0 0 0 0 0 0 0 0 0 0


- However, emacs still tries to re-import the updated keyring when I
restart it

- I was expecting .emacs.d/elpa/gnupg/pubring.gpg to change, but it
  hasn't changed in size, nor has its timestamp. pubring.kbx *has*
  changed however
  
Could this be a gpg issue?

Robert