From: Kei Kebreau <kei@openmailbox.org>
To: guix-devel@gnu.org
Subject: Re: It’s building!
Date: Thu, 12 Jan 2017 11:23:19 -0500 [thread overview]
Message-ID: <86r348xn60.fsf@openmailbox.org> (raw)
In-Reply-To: <8737goz2ba.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 12 Jan 2017 17:10:49 +0100")
[-- Attachment #1: Type: text/plain, Size: 1668 bytes --]
ludo@gnu.org (Ludovic Courtès) writes:
> Hello Guix!
>
> Good news: the new machine, bayfront.guixsd.org, is building Guix master
> for x86_64/i686 with Cuirass⁰!
>
> You can get substitutes from https://bayfront.guixsd.org; just authorize
> its key (with ‘guix archive --authorize’), which is:
>
> (public-key
> (ecc
> (curve Ed25519)
> (q #8D156F295D24B0D9A86FA5741A840FF2D24F60F7B6C4134814AD55625971B394#)))
>
> The machine was initially installed using substitutes from
> hydra.gnu.org, but ever since it has been building stuff on its own (it
> does not offload to any other machine at this point). Thus it can be
> used to check for reproducibility issues:
>
> guix challenge gdk-pixbuf \
> --substitute-urls="https://mirror.hydra.gnu.org https://bayfront.guixsd.org"
>
> The machine runs GuixSD and its config is under version control:
>
> http://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/hydra/bayfront.scm
>
> Currently Cuirass doesn’t expose much over HTTP¹ but hopefully we can
> incrementally add the URLs that guix-hydra.el expects.
>
> There are a few glitches to address, such as the fact that it builds
> with max-jobs = 1 due to <https://bugs.gnu.org/20217>, but we’ll get
> there.
>
> Woohoo! :-)
>
> Ludo’.
>
> ⁰ See <https://www.gnu.org/software/guix/news/growing-our-build-farm.html> and
> <https://lists.gnu.org/archive/html/guix-devel/2017-01/msg00109.html> if
> you missed the previous episodes.
>
> ¹ https://notabug.org/mthl/cuirass/src/master/src/cuirass/http.scm
Wow, this is cool! Thanks to everyone who was/is/will be working on this!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-01-12 16:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 16:10 It’s building! Ludovic Courtès
2017-01-12 16:23 ` Kei Kebreau [this message]
2017-01-12 17:18 ` David Craven
2017-01-12 17:31 ` Alex Sassmannshausen
2017-01-15 22:32 ` Ludovic Courtès
2017-02-01 2:47 ` myglc2
2017-02-09 16:36 ` Archive authentication & ‘guix challenge’ Ludovic Courtès
2017-02-10 22:57 ` myglc2
2017-02-11 14:32 ` Ludovic Courtès
2017-02-11 21:56 ` myglc2
2017-02-13 2:15 ` Maxim Cournoyer
2017-02-13 14:05 ` Ludovic Courtès
2017-02-13 17:13 ` myglc2
2017-02-14 9:20 ` Ludovic Courtès
2017-02-14 15:34 ` myglc2
2017-02-14 16:29 ` Ludovic Courtès
2017-02-14 23:16 ` myglc2
2017-02-14 17:43 ` Maxim Cournoyer
2017-02-14 23:29 ` myglc2
2017-02-14 5:55 ` Maxim Cournoyer
2017-02-10 23:01 ` myglc2
-- strict thread matches above, loose matches on Subject: below --
2017-01-20 6:28 It’s building! Maxim Cournoyer
2017-01-22 13:10 ` ng0
2017-01-22 16:02 ` Ricardo Wurmus
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=86r348xn60.fsf@openmailbox.org \
--to=kei@openmailbox.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).