From: Vagrant Cascadian <vagrant@debian.org>
To: Christopher Baines <mail@cbaines.net>, guix-devel@gnu.org
Subject: Re: Update on bordeaux.guix.gnu.org
Date: Wed, 18 Aug 2021 09:07:35 -0700 [thread overview]
Message-ID: <87y28yu46w.fsf@ponder> (raw)
In-Reply-To: <87eeargf1q.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
On 2021-08-18, Christopher Baines wrote:
> Around 2 months ago, bordeaux.guix.gnu.org came in to existence [1][2].
>
> 1: https://guix.gnu.org/en/blog/2021/substitutes-now-also-available-from-bordeauxguixgnuorg/
> 2: https://lists.gnu.org/archive/html/guix-devel/2021-06/msg00044.html
>
> This took work I'd done on providing substitutes back in 2020 and
> attempted to bring benefits from that to normal users of Guix.
>
> Unfortunately, I don't really know if this has been much of a
> success.
I can definitely speak from experience the likelihood of actually
getting substitutes for any aarch64 linux-libre* packages has gone from
"rarely" to "usually", so it has definitely been a huge improvement for
aarch64, where building locally on most aarch64 hardware is very slow.
Does it have faster build machines? Does it keep retrying until it
succeeds? Building linux-libre* packages for ci.guix.gnu.org usually
timeout when building the source due to long periods with no output...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2021-08-18 16:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 11:36 Update on bordeaux.guix.gnu.org Christopher Baines
2021-08-18 16:07 ` Vagrant Cascadian [this message]
2021-08-18 16:39 ` Christopher Baines
-- strict thread matches above, loose matches on Subject: below --
2021-11-24 8:52 Christopher Baines
2021-11-28 17:26 ` Ludovic Courtès
2021-11-28 19:54 ` Ricardo Wurmus
2021-12-01 17:42 ` Ludovic Courtès
2021-12-01 22:04 ` Ricardo Wurmus
2021-12-03 10:17 ` Christopher Baines
2021-12-03 11:18 ` Ricardo Wurmus
2021-12-03 9:39 ` Christopher Baines
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=87y28yu46w.fsf@ponder \
--to=vagrant@debian.org \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.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.
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.