unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu <matf@disr.it>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 52767@debbugs.gnu.org
Subject: bug#52767: Unexpected problem with Guix System installer
Date: Sat, 12 Nov 2022 23:51:37 +0100	[thread overview]
Message-ID: <aeb9ae3e-050a-44df-8d5f-438e3519af1f@disroot.org> (raw)
In-Reply-To: <87y1sguo4n.fsf@gnu.org>

Hi Mathieu,

Good news about the new features of the installer, thanks for your work! I rarely use that machine but I am now wondering if I haven't managed to install Guix on it, in the end. If that is correct, and working fine, I doubt I will reinstall from scratch, but if it is not running Guix already, then I will let you know when I try again (it may be in weeks or months though).

That machine was supposed to be my test bed before deciding if I could migrate my main hardware to Guix, which I did a few months later.  

Cheers,

Mathieu

On 2022-11-12 17:35 Mathieu Othacehe <othacehe@gnu.org> wrote:

>  
> Hello Mathieu,
>  
>> This is not the drive that was used to boot the Guix installer in
>> the
>> first place.
>>  
>> Thanks, hope someone can understand what the issue is.
>  
> Sorry for the very late reply. We recently added a bunch of error
> reporting features to the installer. Any chance you still have the
> hardware around and would be able to test again using the latest
> installation image available here:
> https://guix.gnu.org/en/download/latest/?
>  
> That would be super useful for us :)
>  
> Thanks,
>  
> Mathieu




      reply	other threads:[~2022-11-12 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <nmail.3.39.61c52656.4f4ef005.4062@debian-sid>
2021-12-24  1:46 ` bug#52767: Unexpected problem with Guix System installer Mathieu
2021-12-24 11:15   ` Julien Lepiller
2022-11-12 16:35   ` Mathieu Othacehe
2022-11-12 22:51     ` Mathieu [this message]

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=aeb9ae3e-050a-44df-8d5f-438e3519af1f@disroot.org \
    --to=matf@disr.it \
    --cc=52767@debbugs.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).