unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Benjamin Slade <slade@jnanam.net>
Cc: help-guix@gnu.org, "Clément Lassieur" <clement@lassieur.org>
Subject: Re: Guix on aarch64
Date: Tue, 21 Aug 2018 13:44:44 -0400	[thread overview]
Message-ID: <87efer4nsj.fsf@netris.org> (raw)
In-Reply-To: <87lg90mh2f.fsf@jnanam.net> (Benjamin Slade's message of "Mon, 20 Aug 2018 23:20:24 -0600")

Benjamin Slade <slade@jnanam.net> writes:

> On 2018-08-20T22:38:20-0600, Leo Famulari <leo@famulari.name> wrote:
>
>  > Having to build tar from the bootstrap binaries suggests you didn't
>  > get any pre-built "substitutes", but instead were building every
>  > package up to emacs and certbot from source.  Aarch64 substitutes
>  > *should* be available from <https://berlin.guixsd.org>.
>  > https://www.gnu.org/software/guix/manual/en/html_node/Binary-Installation.html#index-substitutes_002c-authorization-thereof
>
> I have followed that page in the manual (and just repeated now just in
> case) to make sure both hydra.gnu.org.pub (though I think it should be
> authorised by default) and hydra.gnu.org.pub are authorised,

Did you mean to write "berlin.guixsd.org.pub" above?  That's the key you
would need to authorise to find substitutes for aarch64.

       Mark

  reply	other threads:[~2018-08-21 18:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16 15:27 Guix on aarch64 Benjamin Slade
2018-08-16 16:50 ` Clément Lassieur
2018-08-16 17:33   ` Benjamin Slade
2018-08-16 17:41   ` Benjamin Slade
2018-08-20 17:51     ` Mark H Weaver
2018-08-21  3:52       ` Benjamin Slade
2018-08-21  4:38         ` Leo Famulari
2018-08-21  5:20           ` Benjamin Slade
2018-08-21 17:44             ` Mark H Weaver [this message]
2018-08-21 21:31               ` Benjamin Slade

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=87efer4nsj.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=clement@lassieur.org \
    --cc=help-guix@gnu.org \
    --cc=slade@jnanam.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).