all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: substitutes
Date: Wed, 27 Dec 2017 21:36:14 +0200	[thread overview]
Message-ID: <20171227193614.GA7221@macbook41> (raw)
In-Reply-To: <20171226220616.GA15304@jasmine.lan>

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

On Tue, Dec 26, 2017 at 05:06:16PM -0500, Leo Famulari wrote:
> On Tue, Dec 26, 2017 at 09:43:22PM +0100, Catonano wrote:
> > 2017-12-26 20:09 GMT+01:00 Leo Famulari <leo@famulari.name>:
> > > If Efraim is just providing a substitute mirror of hydra.gnu.org, you
> > > don't need to do anything. If he is building his own binary substitutes,
> > > you'll need the signing key for his server, which wil be provided by
> > > him. I've copied him on this message.
> > 
> > Ah. Thanks
> 
> I forgot to include him directly, so I'm doing it now.

In this case Catonano was looking for the linux-libre 4.13.2 (?)
tarball, which I had a copy of. I don't actually have a local mirror of
hydra, its on my aarch64 substitute server.

> 
> > I just run this line
> > ~$ ./pre-inst-env guix system disk-image gnu/system/install.scm
> > 
> > as by the instrctions to build an installation image from that branch
> > 
> > and I ended up with the error I reported here
> > 
> > If an installation image with the graphical installer can be built with a
> > more current kernel, I'm all for it
> > Only, please, tell me how
> 
> From the folder where you run that command, can you do `git describe`
> and send the result here? Once I'm sure what branch and commit you are
> using, I'll try updating the branch on Savannah.



-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

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

      parent reply	other threads:[~2017-12-27 19:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-26  7:17 substitutes Catonano
2017-12-26 19:09 ` substitutes Leo Famulari
2017-12-26 20:43   ` substitutes Catonano
2017-12-26 20:43     ` substitutes Catonano
2017-12-26 22:06     ` substitutes Leo Famulari
2017-12-27  9:02       ` substitutes Catonano
2017-12-27 19:36         ` substitutes Efraim Flashner
2017-12-27 23:07         ` substitutes Leo Famulari
2017-12-28  2:58           ` substitutes Catonano
2017-12-28  4:58             ` Graphical installer branch Leo Famulari
2017-12-28 14:36               ` Catonano
2017-12-28 14:44                 ` Danny Milosavljevic
2017-12-28 14:45                 ` Danny Milosavljevic
2017-12-28 21:28                   ` Catonano
2017-12-28 21:43                     ` Danny Milosavljevic
2017-12-28 21:54                       ` Catonano
2017-12-28 21:58                       ` Mathieu Othacehe
2017-12-31  6:02                         ` Catonano
2018-01-01 22:09                           ` Hartmut Goebel
2017-12-31 17:30               ` Ricardo Wurmus
2017-12-28  5:01             ` substitutes Efraim Flashner
2017-12-28 14:34               ` substitutes Catonano
2017-12-27 19:36       ` Efraim Flashner [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171227193614.GA7221@macbook41 \
    --to=efraim@flashner.co.il \
    --cc=help-guix@gnu.org \
    --cc=leo@famulari.name \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.