all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org, Benjamin Slade <beoram@gmail.com>
Subject: Re: Guix on aarch64
Date: Tue, 28 Aug 2018 11:40:42 -0400	[thread overview]
Message-ID: <87d0u2ijnp.fsf@netris.org> (raw)
In-Reply-To: <20180828100032.GA1973@jurong> (Andreas Enge's message of "Tue, 28 Aug 2018 12:00:32 +0200")

Andreas Enge <andreas@enge.fr> writes:

> Hello,
>
> On Tue, Aug 28, 2018 at 09:57:49AM +0200, Ricardo Wurmus wrote:
>> I can remove one of the build machines from Berlin.
>
> would this not aggravate the problem with the availability of substitutes?
> As I understand it, then we would have two separate machines, each of
> which would build the same packages; and if two machines are not enough
> to keep up with the pace of development, with only one things should become
> even worse. So if we move machines, maybe we should move both of them for a
> little while, until the proposed changes to cuirass and the berlin storage
> architecture are implemented?

I agree.  I think it would be very bad to split the two machines up.  It
would effectively halve the already unsufficient build capacity on that
architecture.  I'd rather keep them both on Berlin than to split them
up.

      Mark

  reply	other threads:[~2018-08-28 15:42 UTC|newest]

Thread overview: 33+ 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
2018-08-21 21:31               ` Benjamin Slade
2018-08-23  4:58     ` Mark H Weaver
2018-08-23 16:09       ` Benjamin Slade
2018-08-24 10:32       ` Ludovic Courtès
2018-08-24 19:18         ` Ricardo Wurmus
2018-08-26 16:13         ` Mark H Weaver
2018-08-26 18:59           ` Leo Famulari
2018-08-27  8:04             ` Ricardo Wurmus
2018-08-27 18:54               ` Mark H Weaver
2018-08-27 19:11               ` Mark H Weaver
2018-08-27 19:26                 ` Ricardo Wurmus
2018-08-27 21:05                   ` Mark H Weaver
2018-08-27 21:56                     ` Mark H Weaver
2018-08-28  5:39                     ` Mark H Weaver
2018-08-28  7:57                     ` Ricardo Wurmus
2018-08-28 10:00                       ` Andreas Enge
2018-08-28 15:40                         ` Mark H Weaver [this message]
2018-08-28 19:09                       ` Leo Famulari
2018-08-28 19:22                         ` Mark H Weaver
2018-08-27 19:50               ` Leo Famulari
2018-08-27 20:37                 ` Ricardo Wurmus
2018-08-29 20:52               ` Joshua Branson
2018-08-30 20:47                 ` Ricardo Wurmus
2018-08-30  9:49           ` Ludovic Courtès

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=87d0u2ijnp.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=andreas@enge.fr \
    --cc=beoram@gmail.com \
    --cc=guix-devel@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.
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.