unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Mon, 13 Feb 2017 21:55:35 -0800	[thread overview]
Message-ID: <87r3312u5k.fsf@gmail.com> (raw)
In-Reply-To: <8760kefaoc.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 13 Feb 2017 15:05:39 +0100")

[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]

Hello Ludovic,

ludo@gnu.org (Ludovic Courtès) writes:

> Hi Maxim,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>
>> ludo@gnu.org (Ludovic Courtès) writes:
>>
>>> myglc2 <myglc2@gmail.com> skribis:
>>>
>>>> On 02/09/2017 at 17:36 Ludovic Courtès writes:
>>>
>>> [...]
>>>
>>>>> Could it be that the ‘guix archive’ you ran uses a configuration
>>>>> directory other than this one?  What does:
>>>>>
>>>>>   guile -c '(use-modules (guix config)) (pk %config-directory)'
>>>>>
>>>>> print?
>>
>> I remember being equally confused by not finding the key imported in the
>> /etc/guix/acl file, as per the manual.
>>
>> On my GuixSD system, the value of %config-directory is:
>> "/usr/local/etc/guix", and the file "/usr/local/etc/guix/acl" does
>> contain multiple times the public key of Bayfront, which must be due
>> to passed attempts at adding the Bayfront key using "guix archive".
>
> I suppose that’s because you installed Guix in /usr/local at some point?
>

Not that I'm aware of. Like myglc2, I installed GuixSD from the USB
bootable image, following the manual instructions (guix system init or
similar).

It seems that both myglc2 and I are running guix from a git
checkout. Could this has something to do with it?

Thanks,

Maxim

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2017-02-14  5:55 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
2017-02-14 23:29                   ` myglc2
2017-02-14  5:55             ` Maxim Cournoyer [this message]
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=87r3312u5k.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).