Subject: Re: bug#71918: [DOCUMENTATION] the suggested key import method for `guix refresh` doesn't work

From: Ludovic Courtès <[email-masked]>
Date: Wed, 24 Jul 2024 23:44:02 +0200

Hi,

Attila Lendvai <[email-masked]> skribis:

> i was trying to:
>
> $ ./pre-inst-env guix refresh --update dropbear
>
> but the key is not imported, because "no user ID". apparently some keyservers drop the user id for privacy reasons.

Yes, that’s the case of keys.openpgp.org, unless the user explicitly
consented to publishing user ID packets:

  https://keys.openpgp.org/about

> then i went to the manual, and it suggests:
> 
> $ gpg --export [email-masked] | kbxutil --import-openpgp >> mykeyring.kbx

[...]

> i.e. what the manual suggests results in a different file format than what guix refresh creates/expects.

Ouch.  (I’m pretty sure I tested it back then, maybe something changed?)

Since that part is not so useful anyway, how about dropping the now
incorrect bit about kbxutil, like so:

diff --git a/doc/guix.texi b/doc/guix.texi
index 9ba96af459..7323931bad 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -15050,14 +15050,7 @@ Invoking guix refresh
 missing keys are downloaded to this keyring as well (see
 @option{--key-download} below).
 
-You can export keys from your default GPG keyring into a keybox file using
-commands like this one:
-
-@example
-gpg --export rms@@gnu.org | kbxutil --import-openpgp >> mykeyring.kbx
-@end example
-
-Likewise, you can fetch keys to a specific keybox file like this:
+You can fetch keys to a specific keybox file like this:
 
 @example
 gpg --no-default-keyring --keyring mykeyring.kbx \

?

Thanks,
Ludo’.