From: Christopher Howard <christopher@librehacker.com>
To: Rodion Goritskov <rodion.goritskov@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Florian Pelz" <pelzflorian@pelzflorian.de>,
72577@debbugs.gnu.org,
"Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
"Matthew Trzcinski" <matt@excalamus.com>
Subject: [bug#72577] [PATCH v2] services: agate: Change variable names and add system test.
Date: Fri, 16 Aug 2024 11:08:48 -0800 [thread overview]
Message-ID: <8734n4thdr.fsf@librehacker.com> (raw)
In-Reply-To: Christopher Howard's message of "Fri, 16 Aug 2024 09:52:29 -0800 (1 hour, 11 minutes, 4 seconds ago)"
Another little detail perhaps worth noting: the guix documentation specifies that if no valid key and certificate is available, then Agate will try to generate them on its own. However, if you attempt to go this route, you get an error:
```
2024-08-16 10:58:21 No keys or certificates were found in the given directory.
2024-08-16 10:58:21 Specify the --hostname option to generate these automatically.
```
But there does not appear to be a hostname field available to agate-configuration, or at least it is not documented. Only the "hostnames" field for virtual hosts.
--
Christopher Howard
next prev parent reply other threads:[~2024-08-16 19:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-11 14:32 [bug#72577] [PATCH 0/1] services: agate: Change variable names and add system test Rodion Goritskov
2024-08-11 14:40 ` [bug#72577] [PATCH 1/1] " Rodion Goritskov
2024-08-12 5:31 ` [bug#72577] [PATCH v2] " Rodion Goritskov
2024-08-16 17:52 ` Christopher Howard
2024-08-16 19:05 ` Rodion Goritskov
2024-08-16 19:08 ` Christopher Howard [this message]
2024-08-16 19:14 ` Rodion Goritskov
2024-08-16 21:11 ` [bug#72577] [PATCH v3 0/1] " Rodion Goritskov
2024-08-16 21:11 ` [bug#72577] [PATCH v3 1/1] " Rodion Goritskov
2024-08-31 17:06 ` bug#72577: " Ludovic Courtès
2024-08-20 21:42 ` [bug#72577] " Christopher Howard
2024-08-20 23:10 ` Christopher Howard
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=8734n4thdr.fsf@librehacker.com \
--to=christopher@librehacker.com \
--cc=72577@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=matt@excalamus.com \
--cc=maxim.cournoyer@gmail.com \
--cc=pelzflorian@pelzflorian.de \
--cc=rodion.goritskov@gmail.com \
/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.