From: Pierre Neidhardt <mail@ambrevar.xyz>
To: edk@beaver-labs.com, help-guix@gnu.org
Subject: Re: Guix doesnt use guix publish as a substitute
Date: Wed, 02 Sep 2020 10:30:15 +0200 [thread overview]
Message-ID: <87o8mo4m3s.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87eenk8xm6.fsf@rdklein.fr>
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
Hi!
Did you authorize the substitute server on the client?
From the manual (Invoking `guix publish'):
> The signing key pair must be generated before ‘guix publish’ is
> launched, using ‘guix archive --generate-key’ (*note Invoking guix
> archive::).
> ...
> Once a publishing server has been authorized (*note Invoking guix
> archive::), the daemon may download substitutes from it:
Hope that helps!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-09-02 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 7:08 Guix doesnt use guix publish as a substitute edk
2020-09-02 8:30 ` Pierre Neidhardt [this message]
2020-09-02 8:56 ` edk
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=87o8mo4m3s.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=edk@beaver-labs.com \
--cc=help-guix@gnu.org \
/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).