From: Julien Lepiller <julien@lepiller.eu>
To: raingloom <raingloom@riseup.net>,Ricardo Wurmus <rekado@elephly.net>
Cc: 45911@debbugs.gnu.org
Subject: bug#45911: authorized-fields is not/badly documented
Date: Sat, 16 Jan 2021 22:17:25 -0500 [thread overview]
Message-ID: <936E2328-4662-4330-8BCA-50037B7CE3D7@lepiller.eu> (raw)
In-Reply-To: <20210117013449.1192d841@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
I think you need to pass a file-like object, not a scheme expression. Don't try to modify or interpret the public key file, just pass it directly as-is.
Le 16 janvier 2021 19:34:49 GMT-05:00, raingloom <raingloom@riseup.net> a écrit :
>On Sat, 16 Jan 2021 07:10:47 +0100
>Ricardo Wurmus <rekado@elephly.net> wrote:
>
>> raingloom <raingloom@riseup.net> writes:
>>
>> > 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
>>
>> That’s right. It’s a field of guix-configuration, which is
>documented
>> in 10.8.1 Base Services.
>>
>
>Thanks, I found that out already, that's how I ran into the other
>issues.
>I'm still confused about what the proper way to store the config info
>is. Like how I should even store it as Scheme source code.
[-- Attachment #2: Type: text/html, Size: 1427 bytes --]
next prev parent reply other threads:[~2021-01-17 3:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 3:16 bug#45911: authorized-fields is not/badly documented raingloom
2021-01-16 6:10 ` Ricardo Wurmus
2021-01-17 0:34 ` raingloom
2021-01-17 3:17 ` Julien Lepiller [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=936E2328-4662-4330-8BCA-50037B7CE3D7@lepiller.eu \
--to=julien@lepiller.eu \
--cc=45911@debbugs.gnu.org \
--cc=raingloom@riseup.net \
--cc=rekado@elephly.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).