emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#44520: closed (Graphical installer issues on 1.2.0.)


From: GNU bug Tracking System
Subject: bug#44520: closed (Graphical installer issues on 1.2.0.)
Date: Tue, 10 Nov 2020 13:54:02 +0000

Your message dated Tue, 10 Nov 2020 14:53:49 +0100
with message-id <87pn4ll3ma.fsf@gnu.org>
and subject line Re: bug#44520: Graphical installer issues on 1.2.0.
has caused the debbugs.gnu.org bug report #44520,
regarding Graphical installer issues on 1.2.0.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
44520: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=44520
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: Graphical installer issues on 1.2.0. Date: Sun, 08 Nov 2020 16:29:53 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
Hello,

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.

* 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).

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

An unpleasant sunday afternoon testing :(.

Mathieu

Attachment: backtrace.jpg
Description: JPEG image

Attachment: config.jpg
Description: JPEG image

Attachment: bootstrap.jpg
Description: JPEG image


--- End Message ---
--- Begin Message --- Subject: Re: bug#44520: Graphical installer issues on 1.2.0. Date: Tue, 10 Nov 2020 14:53:49 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
Hello,

I tried again on commit 86e9e5c using an image built by the CI and an
image built locally. I was not able to reproduce any of the issues I had
initially.

Closing this one until we find a reproducible way to trigger those
issues.

Thanks,

Mathieu


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]