all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: raingloom <raingloom@riseup.net>
To: 45911@debbugs.gnu.org
Subject: bug#45911: authorized-fields is not/badly documented
Date: Sat, 16 Jan 2021 04:16:15 +0100	[thread overview]
Message-ID: <20210116041615.27cfa112@riseup.net> (raw)

guix archive --authorize started issuing a warning some time ago
pointing to "authorized-keys" in "operating-system".

* that is not a valid field of operating-system
* there is no such item in the Guix info page's index
* the relevant example loads a single key from a file, without
  indicating what the syntax of the file is
* trying to store /etc/guix/signing-key.pub as a Scheme file results in
  a parser error due to the hexadecimal syntax being incompatible with
  some Scheme syntax weirdness

So, how the hecc do I add keys permanently the Official Way? Because I
have no idea. I'll try to update the docs when I figure it out.
OOoor... the person who introduced the change could document it. :|




             reply	other threads:[~2021-01-16  3:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-16  3:16 raingloom [this message]
2021-01-16  6:10 ` bug#45911: authorized-fields is not/badly documented Ricardo Wurmus
2021-01-17  0:34   ` raingloom
2021-01-17  3:17     ` Julien Lepiller
2021-01-17  3:24     ` Julien Lepiller
2021-01-20 20:34       ` raingloom
2021-01-20 21:15         ` Julien Lepiller
2021-01-20  8:49     ` Ludovic Courtès
2021-01-23  5:39       ` raingloom
2021-01-23  9:10         ` Ricardo Wurmus
2021-01-25 17:15           ` raingloom
2021-01-26  7:13             ` Ricardo Wurmus

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=20210116041615.27cfa112@riseup.net \
    --to=raingloom@riseup.net \
    --cc=45911@debbugs.gnu.org \
    /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/guix.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.