From: Robert Pluim <rpluim@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: master 26f9a77: * etc/package-keyring.gpg: Add the 2019 key
Date: Sat, 27 Apr 2019 09:33:03 +0200 [thread overview]
Message-ID: <m2pnp7gaxc.fsf@gmail.com> (raw)
In-Reply-To: <jwvef5or7xu.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 26 Apr 2019 13:38:30 -0400")
>>>>> On Fri, 26 Apr 2019 13:38:30 -0400, Stefan Monnier <monnier@iro.umontreal.ca> said:
>> 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.
Stefan> Huh? That's a bug. Sounds like a false positive for
Stefan> epa-file-handler.
auto-mode-alist has ("\\.gpg\\(~\\|\\.~[0-9]+~\\)?\\'" nil epa-file)
, so Iʼm not too surprised.
>> - 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
Stefan> Hmm... I guess the key was added to that keyring
Stefan> beforehand anyway, so your pubring.gpg isn't modified and
Stefan> hence it stays older than the file in
Stefan> gnu-elpa-keyring-update.
Yes, that sounds about right.
Stefan> OK, thanks, I think I should be able to reproduce both the
Stefan> above problems.
I can test whatever you come up with.
Robert
next prev parent reply other threads:[~2019-04-27 7:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190423203703.26844.27107@vcs0.savannah.gnu.org>
[not found] ` <20190423203704.C1B1F207D5@vcs0.savannah.gnu.org>
2019-04-26 8:22 ` master 26f9a77: * etc/package-keyring.gpg: Add the 2019 key Robert Pluim
2019-04-26 11:57 ` Stefan Monnier
2019-04-26 14:17 ` Robert Pluim
2019-04-26 14:45 ` Robert Pluim
2019-04-26 17:38 ` Stefan Monnier
2019-04-27 7:33 ` Robert Pluim [this message]
2019-04-29 21:20 ` Stefan Monnier
2019-04-30 7:33 ` Robert Pluim
2019-04-30 9:25 ` Robert Pluim
2019-04-30 12:09 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2pnp7gaxc.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.