From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Advice about GuixSD on Serveraptor?
Date: Fri, 24 Mar 2017 11:26:31 -0400 [thread overview]
Message-ID: <20170324152631.GA28369@jasmine> (raw)
In-Reply-To: <87shm3yq2f.fsf@gnu.org>
On Fri, Mar 24, 2017 at 10:36:08AM +0100, Ludovic Courtès wrote:
> Hi!
>
> Leo Famulari <leo@famulari.name> skribis:
>
> > On Wed, Mar 22, 2017 at 01:20:53PM -0400, Leo Famulari wrote:
> >> It's not a bad idea to build it on Hydra. Hydra already builds a
> >> usb-image / disk-image job [0], so we could add a qemu-image job, too.
> >
> > Actually, we used to build a qemu-image on Hydra, but we removed because
> > it was troublesome and unused.
> >
> > https://git.savannah.gnu.org/cgit/guix.git/commit/?id=a3a27745013f3e5a287de3bf0187b2f72beb6965
> >
> > Maybe we should try again :)
>
> Yup, we could reinstate it if needed. That said, we wouldn’t too many
> downloads from hydra.gnu.org…
If we took that route, I'd point the Serveraptor admin to the Hydra link
and ask them to download it once themselves, rather than having each
client download it.
But, making a qemu-image at each evaluation is not so good for
general distribution, because we won't have tested it as thoroughly as
the release image. We'd want the qemu-image to build only if all the
system tests passed.
next prev parent reply other threads:[~2017-03-24 15:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 18:36 GuixSD on commodity hosting platforms, hoster: IN-Berlin ng0
2017-02-09 20:38 ` Jan Nieuwenhuizen
2017-02-10 15:35 ` Ludovic Courtès
2017-02-10 22:48 ` ng0
2017-02-10 22:59 ` ng0
2017-02-11 10:37 ` Jan Nieuwenhuizen
2017-02-11 13:35 ` ng0
2017-02-13 21:47 ` Leo Famulari
2017-02-14 9:24 ` Ludovic Courtès
2017-02-14 10:10 ` ng0
2017-02-14 16:42 ` Leo Famulari
2017-02-16 15:34 ` Christopher Allan Webber
2017-03-13 0:32 ` Advice about GuixSD on Serveraptor? Leo Famulari
2017-03-21 18:06 ` Leo Famulari
2017-03-21 20:22 ` Christopher Allan Webber
2017-03-21 20:46 ` Leo Famulari
2017-03-21 20:53 ` Leo Famulari
2017-03-22 7:36 ` Thomas Danckaert
2017-03-22 17:17 ` Leo Famulari
2017-03-22 12:04 ` Ricardo Wurmus
2017-03-22 17:20 ` Leo Famulari
2017-03-22 17:23 ` Leo Famulari
2017-03-24 9:36 ` Ludovic Courtès
2017-03-24 15:26 ` Leo Famulari [this message]
2017-03-26 10:20 ` Ludovic Courtès
2017-03-21 21:06 ` ng0
2017-03-22 17:15 ` Leo Famulari
2017-03-22 19:20 ` ng0
2017-03-22 21:01 ` ng0
2017-03-24 4:35 ` Chris Marusich
2017-03-24 16:34 ` ng0
2017-03-25 9:01 ` Chris Marusich
2017-03-26 10:26 ` Ludovic Courtès
2017-03-26 11:54 ` ng0
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=20170324152631.GA28369@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ludo@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).