unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: <ng0@pragmatique.xyz>
To: ng0 <ng0@pragmatique.xyz>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: The broken 0.13 release for GuixSD
Date: Wed, 24 May 2017 10:41:22 +0200 (CEST)	[thread overview]
Message-ID: <E1dDRr8-0002CN-9b@rmmprod05.runbox> (raw)
In-Reply-To: <E1dDRCP-0008Ir-SN@rmmprod05.runbox>

On Wed, 24 May 2017 09:59:17 +0200 (CEST), <ng0@pragmatique.xyz> wrote:

> 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.
> 
> 
> Last I will try today is create an install target from this 0.13 resembling
> machine I'm writing on right now, to see if this magically fixes the tests.


Wow, this is fckd up. You know how I made the install pass (or at least go
beyond the point of the test failing)?

guix pull; guix environment --ad-hoc guix
in environment: guix system init /mnt/etc/config.scm /mnt

what?

  reply	other threads:[~2017-05-24  8:41 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 [this message]
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
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=E1dDRr8-0002CN-9b@rmmprod05.runbox \
    --to=ng0@pragmatique.xyz \
    --cc=guix-devel@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).