all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: bo0od <bo0od@riseup.net>
Cc: 47714@debbugs.gnu.org
Subject: bug#47714: Cutting the internet in guix installation will stop the installation permanently (irreversible)
Date: Wed, 27 Dec 2023 14:03:38 +0100	[thread overview]
Message-ID: <87bkabre51.fsf@pelzflorian.de> (raw)
In-Reply-To: <3fa73763-a4a5-f252-881d-9813b2f7614b@riseup.net> (bo0od@riseup.net's message of "Mon, 12 Apr 2021 00:12:59 +0000")

bo0od <bo0od@riseup.net> writes:
> Hi There,
>
> Try install guix with manual installation while its on the end step
> (downloading things which mentioned in config.csm) cut the internet
> off, It will not reback you to the terminal so that you can
> repeat/relaunch the installation/downloading from where it stopped but
> rather will give you stuck/freeze screen.
>
> ThX!

I would like to close this bug.

Does the same issue affect installing software with Guix on an already
installed system?  If it only affects the installer, there might be a
valid issue with Guix’ cow-store service.

Otherwise, I guess this is not a Guix bug.  Stuck/freeze during manual
installation sounds like a kernel bug or like not properly mounting the
file systems.  Some unrelated Ethernet issues (with getting curlftpfs to
start automatically) disappear for my machine when installing non-free
Realtek firmware, which is not a solution, but this is likely not a Guix
bug but an issue with the linux-libre kernel.

Will close in two weeks.

Regards,
Florian




  reply	other threads:[~2023-12-27 13:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12  0:12 bug#47714: Cutting the internet in guix installation will stop the installation permanently (irreversible) bo0od
2023-12-27 13:03 ` pelzflorian (Florian Pelz) [this message]
2024-01-11 13:57   ` pelzflorian (Florian Pelz)

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=87bkabre51.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=47714@debbugs.gnu.org \
    --cc=bo0od@riseup.net \
    /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.