unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Thomas Danckaert <post@thomasdanckaert.be>
To: rekado@elephly.net
Cc: help-guix@gnu.org, help-guix-bounces+swedebugia=riseup.net@gnu.org
Subject: Re: very few substitutes available?
Date: Fri, 11 Jan 2019 22:26:02 +0100 (CET)	[thread overview]
Message-ID: <20190111.222602.644498626993726255.post@thomasdanckaert.be> (raw)
In-Reply-To: <87y37xrb9d.fsf@elephly.net>

From: Ricardo Wurmus <rekado@elephly.net>
Subject: Re: very few substitutes available?
Date: Sun, 06 Jan 2019 17:39:26 +0100

> Double check that the key for ci.guix.info is in fact authorized.
> You can look at /etc/guix/acl and/or run “guix archive --authorize <
> ~/.config/guix/current/share/guix/ci.guix.info.pub”.

How can I see if my /etc/guix/acl is ok?  I see a sexp with what looks
like a list containing a single (public-key (rsa (n [...]) (e
[...]))).  Is it normal to have just a single public-key in that list
(I had expected 2 or 3, or hydra, berlin, and ci.guix.info)?

Is it still ok to have "https://berlin.guixsd.org" in the list of
substitute-urls of my guix daemon service?

Thomas

  reply	other threads:[~2019-01-11 21:32 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 [this message]
2019-01-11 22:07         ` Leo Famulari
2019-01-12  7:11         ` 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=20190111.222602.644498626993726255.post@thomasdanckaert.be \
    --to=post@thomasdanckaert.be \
    --cc=help-guix-bounces+swedebugia=riseup.net@gnu.org \
    --cc=help-guix@gnu.org \
    --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.
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).