From: Thorsten Wilms <t_w_@freenet.de>
To: Thomas Danckaert <post@thomasdanckaert.be>, jonathan.brielmaier@web.de
Cc: guix-devel@gnu.org, help-guix@gnu.org
Subject: Re: hydra.gnu.org off-line for maintenance
Date: Fri, 26 Oct 2018 11:46:03 +0200 [thread overview]
Message-ID: <47cf3cd8-8c84-9ec8-1a36-b7983ca0318b@freenet.de> (raw)
In-Reply-To: <20181026.112833.1041340413850544457.post@thomasdanckaert.be>
On 26/10/2018 11.28, Thomas Danckaert wrote:
> Also, you may want to add this setting globally and permanently, so you
> don't have to specify it every time you run guix. You can do this by
> passing the option to the guix daemon
>
> - when using guix on another distribution with systemd, you can modify
> the the ExecStart line in /etc/systemd/system/guix-daemon.service as
> follows:
>
> ExecStart=/var/guix/profiles/per-user/root/guix-profile/bin/guix-daemon
> --build-users-group=guixbuild
> "--substitute-urls=https://mirror.hydra.gnu.org https://berlin.guixsd.org"
Shouldn't that be:
---
ExecStart=/var/guix/profiles/per-user/root/guix-profile/bin/guix-daemon
--build-users-group=guixbuild
--substitute-urls="https://mirror.hydra.gnu.org https://hydra.gnu.org
https://berlin.guixsd.org"
---
?
> By the way: when revisiting this issue, I found the manual a bit
> confusing. You'll find all the information you need when you read the
> entire section on substitutes from front to back, but when you just try
> to find specific information using the headlines, it's a bit confusing.
> For example, to learn about --substitute-urls and the daemon settings
> for other substitute servers, you'll need to read "Official Substitute
> Server", which you might not do when looking to add another server. The
> subtitle for "Substitute Server Authorization" says "How to enable or
> disable substitutes", but doesn't give all the information you need to
> enable another substitute server.
>
> If people here agree, I'd be happy to send a documentation patch.
For whatever it may be worth, when I first read about
https://berlin.guixsd.org, I wondered if it could/should be used
additionally, looked at the documentation, found it confusing and then
forgot about the issue.
--
Thorsten Wilms
thorwil's design for free software:
http://thorwil.wordpress.com/
next prev parent reply other threads:[~2018-10-26 9:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 9:57 hydra.gnu.org off-line for maintenance Ludovic Courtès
2018-10-25 22:41 ` Luther Thompson
2018-10-26 6:01 ` Jonathan Brielmaier
2018-10-26 9:28 ` Thomas Danckaert
2018-10-26 9:46 ` Thorsten Wilms [this message]
2018-10-26 13:40 ` Tobias Geerinckx-Rice
2018-10-26 10:06 ` Clément Lassieur
2018-10-26 15:26 ` Alex Vong
2018-10-27 14:49 ` Tobias Geerinckx-Rice
2018-10-31 14:40 ` Alex Vong
2018-10-26 19:21 ` Evaluations on berlin.guixsd.org Ludovic Courtès
2018-11-01 15:07 ` hydra.gnu.org off-line for maintenance Ludovic Courtès
2018-11-01 15:30 ` Pjotr Prins
2018-11-06 11:01 ` Ludovic Courtès
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=47cf3cd8-8c84-9ec8-1a36-b7983ca0318b@freenet.de \
--to=t_w_@freenet.de \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=jonathan.brielmaier@web.de \
--cc=post@thomasdanckaert.be \
/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).