unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 44520@debbugs.gnu.org
Subject: bug#44520: Graphical installer issues on 1.2.0.
Date: Sun, 08 Nov 2020 19:06:58 +0100	[thread overview]
Message-ID: <87tutzu3i5.fsf@gnu.org> (raw)
In-Reply-To: <87sg9j50jy.fsf@gnu.org> (Mathieu Othacehe's message of "Sun, 08 Nov 2020 16:29:53 +0100")

Hi,

Mathieu Othacehe <othacehe@gnu.org> skribis:

> I tried the 1.2.0 graphical installer at ae0fe28, installing Guix System
> from a usb drive to another one.
>
> I had three issues:
>
> * The auto partitioning crashed, backtrace as attachment.

Argh.

> * Using manual partitioning as a work-around, I started the installation
> and observed that the installer downloaded "python" sources and then
> substitutes for the whole bootstrapping chain (also as attachment).

Could it be that these get downloaded due to some “debug” output being
pulled (perhaps unnecessarily so but grafting can do that sometimes)?

> * The substitutes download speed was sometimes super low (~ 50Kb/s).

Yes, unfortunately non-offloaded disk image builds (fixed by recent
commits) along with GC running all day long has a terrible impact on
bandwidth.

It should get a bit better at least now that disk image builds will no
longer happen on the head node, but OTOH there’s still a lot of build
activity happening and that definitely increases pressure.

I look forward to the day where using the Build Coordinator we can
better decouple the build farm from the node running ‘guix publish’.

Thanks,
Ludo’.




  reply	other threads:[~2020-11-08 18:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-08 15:29 bug#44520: Graphical installer issues on 1.2.0 Mathieu Othacehe
2020-11-08 18:06 ` Ludovic Courtès [this message]
2020-11-08 18:53   ` Mathieu Othacehe
2020-11-10 13:53     ` Mathieu Othacehe

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=87tutzu3i5.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=44520@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).