From: <ng0@pragmatique.xyz>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: The broken 0.13 release for GuixSD
Date: Wed, 24 May 2017 13:27:47 +0200 (CEST) [thread overview]
Message-ID: <E1dDUSB-0007Q1-Md@rmmprod06.runbox> (raw)
In-Reply-To: <874lwaa6ud.fsf@elephly.net>
On Wed, 24 May 2017 12:26:34 +0200, Ricardo Wurmus <rekado@elephly.net> wrote:
>
> ng0@pragmatique.xyz writes:
>
> > Going from within GuixSD 0.12 to 0.13 (multiple guix pull issued to get
> > all the dependencies you might lack) works.
> >
> > GuixSD 0.13 medium on new installations, with no system present previously,
> > so far failed on all types of hardware from the last 1 - 15 years for me including
> > bios and uefi systems.
> >
> > All get stuck on the same test.
> > This should not happen at all with a release.
>
> Please, the least you could do when using words like “broken” and
> “should not happen at all” is to be precise about *what* fails.
>
> This is not constructive.
>
> --
> Ricardo
>
> GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
> https://elephly.net
This https://debbugs.gnu.org/cgi/bugreport.cgi?bug=27034 and https://debbugs.gnu.org/cgi/bugreport.cgi?bug=27032 this.
But I can add more duplication and describe what happened in my case:
Situation and Expectation:
uefi and bios (separate "and", not "bios and uefi") computers
No system installed.
GuixSD 0.13 installer should simply work as per instructions and the
way I know it.
Problem:
When you reach the point where you run "guix system init /path/to/config.scm /mnt"
and guix gets build, reaching its 'make check', 2 tests (as linked above) fail.
Solution:
See previous message I wrote here about guix environment --ad-hoc guix.
next prev parent reply other threads:[~2017-05-24 11:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 7:59 The broken 0.13 release for GuixSD ng0
2017-05-24 8:41 ` ng0
2017-05-24 9:17 ` Fox
2017-05-24 9:20 ` ngillmann
2017-05-24 9:24 ` disk order Fox
2017-05-24 9:30 ` ng0
2017-05-24 9:38 ` ng0
2017-05-24 9:58 ` thread hijacking Fox
2017-05-24 10:02 ` ng0
2017-05-24 9:30 ` disk order Vincent Legoll
2017-05-24 9:31 ` Fox
2017-05-24 10:26 ` The broken 0.13 release for GuixSD Ricardo Wurmus
2017-05-24 11:27 ` ng0 [this message]
2017-05-24 11:32 ` Ricardo Wurmus
2017-05-24 11:35 ` Fox
2017-05-24 11:59 ` Ludovic Courtès
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=E1dDUSB-0007Q1-Md@rmmprod06.runbox \
--to=ng0@pragmatique.xyz \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.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 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).