unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Call for 1.2 installer testing.
Date: Tue, 13 Oct 2020 18:40:32 +0200	[thread overview]
Message-ID: <87wnzuhyf3.fsf@gmail.com> (raw)
In-Reply-To: <87h7r3k1qc.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]

Hello,

Here a positive installation experience:

I did my usual bare metal installation of the image linked below on a
ThinkPenguin laptop that has always worked pretty well with Guix.

Ran through the graphical installation, going through configuration
options that have caused problems in the past (Esperanto locale, based
in Brussels, with Neo2 keyboard layout, fully encrypted disk).

The installation proceeded like a charm. Perhaps partly to do with me
now being used to the installer, and having hardware that "just works"
with libre software, but this was super user friendly. And actually also
super fast!

Congratulations and a massive thanks to everyone who's put time and
energy into this!

I can honestly say, with the current state, I would absolutely try a
guix system deployment in the first instance on any laptop I might
consider a GNU\Linux install, and only falling back to Debian if there
are hardware issues.

Very impressed.

Best wishes,

Alex

Mathieu Othacehe <othacehe@gnu.org> writes:

> Hello,
>
> The 1.2 release is on its way. So here's the traditional call for
> installer testing. This time, the CI is building latest installer
> images, which should ease testing.
>
> I propose that we first concentrate our efforts on this image:
> https://ci.guix.gnu.org/download/654 which corresponds to commit
> 29a2eb3.
>
> Testing different partitioning schemes on different hardware is really
> important to spot issues that our virtualized automated installer tests
> would be missing.
>
> Thanks for your help,
>
> Mathieu


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 272 bytes --]

  parent reply	other threads:[~2020-10-13 16:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09 12:44 Call for 1.2 installer testing Mathieu Othacehe
2020-10-11 13:33 ` [PATCH] installer: Add Emacs EXWM desktop environment. [WAS Re: Call for 1.2 installer testing.] Jan Nieuwenhuizen
     [not found]   ` <87h7qym7v2.fsf@gnu.org>
2020-10-13 19:26     ` Jan Nieuwenhuizen
2020-10-13 16:40 ` Alex Sassmannshausen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-10-11  6:23 Call for 1.2 installer testing Brendan Tildesley
2020-10-11  9:48 ` Efraim Flashner
2020-10-11 20:32 ` pelzflorian (Florian Pelz)
2020-10-11 20:36   ` Marinus Savoritias
2020-10-11 23:40   ` Brendan Tildesley
2020-10-13  6:47   ` Brendan Tildesley
2020-10-13  6:50   ` Brendan Tildesley

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=87wnzuhyf3.fsf@gmail.com \
    --to=alex.sassmannshausen@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=othacehe@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).