From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, myglc2 <myglc2@gmail.com>
Subject: Re: Archive authentication & ‘guix challenge’
Date: Tue, 14 Feb 2017 09:43:03 -0800 [thread overview]
Message-ID: <87efz03byw.fsf@gmail.com> (raw)
In-Reply-To: <87vasduo0h.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 14 Feb 2017 10:20:46 +0100")
[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]
Hi George and Ludovic,
ludo@gnu.org (Ludovic Courtès) writes:
[...]
>
> ‘guix pull’ preserves your (guix config) module. So if the ‘guix’ you
> run was configured to use /etc, it’ll keep using that; if it was
> configured to use /usr/local/etc, it’ll keep using that.
>
> If you run “./pre-inst-env guix pull”, then you end up using (guix
> config) from your build tree, which is configured to use /usr/local/etc
> by default. That’s probably what happened, no?
>
I ran guix pull initially (before starting to use a git checkout). And
I remember mistakenly running "guix pull" from my guix checkout, which
if I followed your explanation would have caused (guix config) to point
to /usr/local/etc. So that seems like a plausible explication! I guess
in the newer Guix releases the default path has been fixed (to /etc)?
> To fix it, you can either run:
>
> rm -f ~/.config/guix/latest && guix pull
>
> or just do:
>
> ./configure --sysconfdir=/etc
>
I ran ./configure --localstatedir=/var --sysconfig=/etc && make, and I
can now confirm that it fixed it:
guile -c "(use-modules (guix config)) (pk %config-directory)"
;;; ("/etc/guix")
I also checked that:
sudo guix archive --authorize < bayfront.guixsd.org.pub
Produced an entry in /etc/guix/acl.
George, as an alternative, you might be interested in declaring the extra
key in your system's config.scm file [0].
Thanks for the help, Ludovic!
Maxim
[0] https://lists.gnu.org/archive/html/guix-devel/2017-01/msg01746.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-02-14 17:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 16:10 It’s building! Ludovic Courtès
2017-01-12 16:23 ` Kei Kebreau
2017-01-12 17:18 ` David Craven
2017-01-12 17:31 ` Alex Sassmannshausen
2017-01-15 22:32 ` Ludovic Courtès
2017-02-01 2:47 ` myglc2
2017-02-09 16:36 ` Archive authentication & ‘guix challenge’ Ludovic Courtès
2017-02-10 22:57 ` myglc2
2017-02-11 14:32 ` Ludovic Courtès
2017-02-11 21:56 ` myglc2
2017-02-13 2:15 ` Maxim Cournoyer
2017-02-13 14:05 ` Ludovic Courtès
2017-02-13 17:13 ` myglc2
2017-02-14 9:20 ` Ludovic Courtès
2017-02-14 15:34 ` myglc2
2017-02-14 16:29 ` Ludovic Courtès
2017-02-14 23:16 ` myglc2
2017-02-14 17:43 ` Maxim Cournoyer [this message]
2017-02-14 23:29 ` myglc2
2017-02-14 5:55 ` Maxim Cournoyer
2017-02-10 23:01 ` myglc2
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=87efz03byw.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=myglc2@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 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).