From: "Gábor Boskovits" <boskovits@gmail.com>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Plan for a release!
Date: Fri, 20 Mar 2020 14:13:28 +0100 [thread overview]
Message-ID: <CAE4v=pjf+rP6vXWCj6s59Gt_emvQd-Jx5Jfw41MsAGpMHjCfgA@mail.gmail.com> (raw)
In-Reply-To: <87k13fjo2i.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]
Hello,
Mathieu Othacehe <m.othacehe@gmail.com> ezt írta (időpont: 2020. márc. 20.,
Pén 11:52):
>
> Hey,
>
> >> Done, but it’d be nice to add more test of the installer!
> >
> > I can help on that. Maybe adding:
> >
> > * More partitioning patterns
> > * More DE & services
>
> Turns out, when selecting GNOME in choose-services call of (gnu tests
> install), it triggers downloads during "guix system init ..." call.
>
> I guess it's normal because the installer image does not contain those
> packages. However, as there's no connection, it fails.
>
> Not sure, we can go further?
>
I believe what could be done is to create and extended installer image with
the packages need for testing available.
It could work similarly to how the barebones closure is included right now.
These images would be quite big, and impractical for anything but testing.
I believe that having a simple very big image is better than having
separate smaller ones for testing. This would also allow us to create a
selection of images with different de/service options for direct download
if the need arises, by expanding the list of configuration templates, and
the test image can be simply created by including the closure of all the
template configs. Wdyt?
>
> In the meantime, here's a patch that helps dealing with installation
> failures.
>
> Thanks,
>
> Mathieu
>
Best regards,
g_bor
>
[-- Attachment #2: Type: text/html, Size: 2222 bytes --]
next prev parent reply other threads:[~2020-03-20 13:13 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 21:38 Plan for a release! Ludovic Courtès
2020-02-24 22:55 ` Vincent Legoll
2020-02-25 14:00 ` Jonathan Brielmaier
2020-02-25 15:15 ` Vincent Legoll
2020-02-24 23:35 ` zimoun
2020-02-25 15:47 ` Joshua Branson
2020-03-05 4:54 ` jbranso
2020-03-08 12:04 ` pelzflorian (Florian Pelz)
2020-03-08 21:03 ` kmscon not working on MacBook Ludovic Courtès
2020-03-09 7:43 ` pelzflorian (Florian Pelz)
2020-03-09 9:48 ` Vincent Legoll
2020-03-09 16:45 ` Ludovic Courtès
2020-03-11 7:14 ` pelzflorian (Florian Pelz)
2020-03-11 7:25 ` pelzflorian (Florian Pelz)
2020-03-20 8:48 ` pelzflorian (Florian Pelz)
2020-03-20 8:51 ` pelzflorian (Florian Pelz)
2020-03-25 23:00 ` pelzflorian (Florian Pelz)
2020-03-26 2:26 ` Bengt Richter
2020-03-26 16:53 ` pelzflorian (Florian Pelz)
2020-03-29 10:26 ` pelzflorian (Florian Pelz)
2020-03-08 12:35 ` Gnome takes more than 5 minutes to start Ricardo Wurmus
2020-03-08 21:04 ` Btrfs/udev issue Ludovic Courtès
2020-03-05 13:42 ` Plan for a release! jbranso
2020-03-05 16:45 ` sirgazil
2020-03-06 16:32 ` Joshua Branson
2020-03-05 21:09 ` Jan
2020-03-06 16:33 ` Joshua Branson
2020-03-06 16:51 ` Thunar cannot launch gio-launch-desktop Ricardo Wurmus
2020-03-06 17:57 ` Jan
2020-03-06 21:51 ` Ricardo Wurmus
2020-03-06 23:59 ` Jan
2020-03-07 23:41 ` Jan
2020-03-08 9:08 ` Ricardo Wurmus
2020-03-08 22:05 ` Jan
2020-03-08 23:41 ` Jan
2020-03-09 22:41 ` Jan
2020-03-06 6:44 ` Plan for a release! pelzflorian (Florian Pelz)
2020-03-06 9:58 ` John Soo
2020-03-08 12:33 ` Ricardo Wurmus
2020-03-08 21:10 ` Ludovic Courtès
2020-03-12 13:54 ` Ludovic Courtès
2020-03-18 16:53 ` Ludovic Courtès
2020-03-18 17:31 ` Ricardo Wurmus
2020-03-18 17:49 ` Mathieu Othacehe
2020-03-20 10:52 ` Mathieu Othacehe
2020-03-20 13:13 ` Gábor Boskovits [this message]
2020-03-20 13:58 ` Mathieu Othacehe
2020-03-21 15:46 ` Ludovic Courtès
2020-03-23 14:05 ` Mathieu Othacehe
2020-03-26 11:55 ` Ludovic Courtès
2020-03-26 12:37 ` Vincent Legoll
2020-03-26 14:24 ` 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='CAE4v=pjf+rP6vXWCj6s59Gt_emvQd-Jx5Jfw41MsAGpMHjCfgA@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=m.othacehe@gmail.com \
/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.