From: Ricardo Wurmus <rekado@elephly.net>
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: help-guix@gnu.org, help-guix-bounces+swedebugia=riseup.net@gnu.org
Subject: Re: very few substitutes available?
Date: Sat, 12 Jan 2019 08:11:14 +0100 [thread overview]
Message-ID: <87o98mnyel.fsf@elephly.net> (raw)
In-Reply-To: <20190111.222602.644498626993726255.post@thomasdanckaert.be>
Hi Thomas,
> Is it still ok to have "https://berlin.guixsd.org" in the list of
> substitute-urls of my guix daemon service?
ci.guix.info is the same server as berlin.guixsd.org at the moment. It
uses the same key. If you haven’t authorized that key you won’t get
substitutes from there, no matter which of the two URLs you use.
--
Ricardo
prev parent reply other threads:[~2019-01-12 7:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-05 17:24 very few substitutes available? Thomas Danckaert
2019-01-05 19:39 ` swedebugia
2019-01-06 13:14 ` Thomas Danckaert
2019-01-06 16:39 ` Ricardo Wurmus
2019-01-11 21:26 ` Thomas Danckaert
2019-01-11 22:07 ` Leo Famulari
2019-01-12 7:11 ` Ricardo Wurmus [this message]
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=87o98mnyel.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix-bounces+swedebugia=riseup.net@gnu.org \
--cc=help-guix@gnu.org \
--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.
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).