From: Thomas Danckaert <post@thomasdanckaert.be>
To: rekado@elephly.net
Cc: help-guix@gnu.org
Subject: Re: very old daemon = no substitutes?
Date: Mon, 23 Dec 2019 15:59:16 +0100 (CET) [thread overview]
Message-ID: <20191223.155916.1639715660576449204.post@thomasdanckaert.be> (raw)
In-Reply-To: <87a77jp2e1.fsf@elephly.net>
From: Ricardo Wurmus <rekado@elephly.net>
Subject: Re: very old daemon = no substitutes?
Date: Mon, 23 Dec 2019 15:01:10 +0100
> Double check /etc/guix/acl to make sure that the public key for
> ci.guix.gnu.org is listed there.
Thank you very much! I found the cause of the problem: 'guix archive
--authorize' was updating the file /usr/local/etc/guix/acl instead of
/etc/guix/acl. Manually replacing /etc/guix/acl fixed the problem
(wish I'd found out 2 days ago :-D ).
Any idea why 'guix archive' is looking at /usr/local/...and what I
could do about that?
cheers,
Thomas
next prev parent reply other threads:[~2019-12-23 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 11:53 very old daemon = no substitutes? Thomas Danckaert
2019-12-23 12:14 ` Julien Lepiller
2019-12-23 14:01 ` Ricardo Wurmus
2019-12-23 14:59 ` Thomas Danckaert [this message]
2019-12-23 15:28 ` Fwd: " Tobias Geerinckx-Rice
2019-12-23 18:56 ` 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=20191223.155916.1639715660576449204.post@thomasdanckaert.be \
--to=post@thomasdanckaert.be \
--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).