unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
* The broken 0.13 release for GuixSD
@ 2017-05-24  7:59 ng0
  2017-05-24  8:41 ` ng0
  2017-05-24 10:26 ` The broken 0.13 release for GuixSD Ricardo Wurmus
  0 siblings, 2 replies; 16+ messages in thread
From: ng0 @ 2017-05-24  7:59 UTC (permalink / raw)
  To: guix-devel

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.

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: The broken 0.13 release for GuixSD
  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 10:26 ` The broken 0.13 release for GuixSD Ricardo Wurmus
  1 sibling, 1 reply; 16+ messages in thread
From: ng0 @ 2017-05-24  8:41 UTC (permalink / raw)
  To: ng0; +Cc: guix-devel

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?

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: The broken 0.13 release for GuixSD
  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
  0 siblings, 2 replies; 16+ messages in thread
From: Fox @ 2017-05-24  9:17 UTC (permalink / raw)
  To: guix-devel

never mind the wrong disk order in the part about VM install (qemu)

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: The broken 0.13 release for GuixSD
  2017-05-24  9:17   ` Fox
@ 2017-05-24  9:20     ` ngillmann
  2017-05-24  9:24     ` disk order Fox
  1 sibling, 0 replies; 16+ messages in thread
From: ngillmann @ 2017-05-24  9:20 UTC (permalink / raw)
  To: Fox; +Cc: guix-devel



On Wed, 24 May 2017 11:17:11 +0200, Fox <firefox@firemail.cc> wrote:

> never mind the wrong disk order in the part about VM install (qemu)


What's up with these random messages without context?
As you might know or not know I know my way around in GuixSD and
am not just trying to get started with it.

^ permalink raw reply	[flat|nested] 16+ messages in thread

* disk order
  2017-05-24  9:17   ` Fox
  2017-05-24  9:20     ` ngillmann
@ 2017-05-24  9:24     ` Fox
  2017-05-24  9:30       ` ng0
                         ` (2 more replies)
  1 sibling, 3 replies; 16+ messages in thread
From: Fox @ 2017-05-24  9:24 UTC (permalink / raw)
  To: guix-devel

referring to
https://www.gnu.org/software/guix/manual/guix.html#Installing-GuixSD-in-a-VM


qemu-system-x86_64 -m 1024 -smp 1 \
   -net user -net nic,model=virtio -boot menu=on \
   -drive file=guixsd.img \
   -drive file=guixsd-usb-install-0.13.0.system




will not boot in qemu unless you change it to

qemu-system-x86_64 -m 1024 -smp 1 \
   -net user -net nic,model=virtio -boot menu=on \
   -drive file=guixsd-usb-install-0.13.0.system
   -drive file=guixsd.img \

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: disk order
  2017-05-24  9:24     ` disk order Fox
@ 2017-05-24  9:30       ` ng0
  2017-05-24  9:38         ` ng0
  2017-05-24  9:30       ` disk order Vincent Legoll
  2017-05-24  9:31       ` Fox
  2 siblings, 1 reply; 16+ messages in thread
From: ng0 @ 2017-05-24  9:30 UTC (permalink / raw)
  To: Fox; +Cc: guix-devel

How is that  even related to what I wrote.
That's what I meant with "your message is random and unrelated".

On Wed, 24 May 2017 11:24:42 +0200, Fox <firefox@firemail.cc> wrote:

> referring to
> https://www.gnu.org/software/guix/manual/guix.html#Installing-GuixSD-in-a-VM
> 
> 
> qemu-system-x86_64 -m 1024 -smp 1 \
>    -net user -net nic,model=virtio -boot menu=on \
>    -drive file=guixsd.img \
>    -drive file=guixsd-usb-install-0.13.0.system
> 
> 
> 
> 
> will not boot in qemu unless you change it to
> 
> qemu-system-x86_64 -m 1024 -smp 1 \
>    -net user -net nic,model=virtio -boot menu=on \
>    -drive file=guixsd-usb-install-0.13.0.system
>    -drive file=guixsd.img \

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: disk order
  2017-05-24  9:24     ` disk order Fox
  2017-05-24  9:30       ` ng0
@ 2017-05-24  9:30       ` Vincent Legoll
  2017-05-24  9:31       ` Fox
  2 siblings, 0 replies; 16+ messages in thread
From: Vincent Legoll @ 2017-05-24  9:30 UTC (permalink / raw)
  To: Fox; +Cc: guix-devel

Hello,

On Wed, May 24, 2017 at 11:24 AM, Fox <firefox@firemail.cc> wrote:
> referring to
> https://www.gnu.org/software/guix/manual/guix.html#Installing-GuixSD-in-a-VM
>
> qemu-system-x86_64 -m 1024 -smp 1 \
>   -net user -net nic,model=virtio -boot menu=on \
>   -drive file=guixsd.img \
>   -drive file=guixsd-usb-install-0.13.0.system
>
> will not boot in qemu unless you change it to
>
> qemu-system-x86_64 -m 1024 -smp 1 \
>   -net user -net nic,model=virtio -boot menu=on \
>   -drive file=guixsd-usb-install-0.13.0.system
>   -drive file=guixsd.img \

Careful with that backslash, Eugene (*)...

-- 
Vincent Legoll

^ permalink raw reply	[flat|nested] 16+ messages in thread

* disk order
  2017-05-24  9:24     ` disk order Fox
  2017-05-24  9:30       ` ng0
  2017-05-24  9:30       ` disk order Vincent Legoll
@ 2017-05-24  9:31       ` Fox
  2 siblings, 0 replies; 16+ messages in thread
From: Fox @ 2017-05-24  9:31 UTC (permalink / raw)
  To: guix-devel


> will not boot in qemu unless you change it to
>
> qemu-system-x86_64 -m 1024 -smp 1 \
>   -net user -net nic,model=virtio -boot menu=on \
>   -drive file=guixsd-usb-install-0.13.0.system \
>   -drive file=guixsd.img

slash typo

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: disk order
  2017-05-24  9:30       ` ng0
@ 2017-05-24  9:38         ` ng0
  2017-05-24  9:58           ` thread hijacking Fox
  0 siblings, 1 reply; 16+ messages in thread
From: ng0 @ 2017-05-24  9:38 UTC (permalink / raw)
  To: ng0; +Cc: guix-devel

On Wed, 24 May 2017 11:30:03 +0200 (CEST), <ng0@pragmatique.xyz> wrote:

> How is that  even related to what I wrote.
> That's what I meant with "your message is random and unrelated".
> 
> On Wed, 24 May 2017 11:24:42 +0200, Fox <firefox@firemail.cc> wrote:
> 
> > referring to
> > https://www.gnu.org/software/guix/manual/guix.html#Installing-GuixSD-in-a-VM
> > 
> > 
…

This is a prime example of "people will never learn not to do things like
thread hijacking, cross-posting, etc"...

I'm open for constructive discussion on the original thread (which
for the record was "why do I have to run guix environment --ad-hoc guix"
in the SD installer on baremetal not in a VM"), I will ignore
this hijacked thread now. Please don't include me anymore in replies.
Thanks.

^ permalink raw reply	[flat|nested] 16+ messages in thread

* thread hijacking
  2017-05-24  9:38         ` ng0
@ 2017-05-24  9:58           ` Fox
  2017-05-24 10:02             ` ng0
  0 siblings, 1 reply; 16+ messages in thread
From: Fox @ 2017-05-24  9:58 UTC (permalink / raw)
  To: guix-devel

dude, I did not read past your headline "broken release ..." and I am 
not obliged to.



> This is a prime example of "people will never learn not to do things like
> thread hijacking, cross-posting, etc"...
>
> I'm open for constructive discussion on the original thread (which
> for the record was "why do I have to run guix environment --ad-hoc guix"
> in the SD installer on baremetal not in a VM"), I will ignore
> this hijacked thread now. Please don't include me anymore in replies.
> Thanks.

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: thread hijacking
  2017-05-24  9:58           ` thread hijacking Fox
@ 2017-05-24 10:02             ` ng0
  0 siblings, 0 replies; 16+ messages in thread
From: ng0 @ 2017-05-24 10:02 UTC (permalink / raw)
  To: guix-devel



On Wed, 24 May 2017 11:58:36 +0200, Fox <firefox@firemail.cc> wrote:

> dude, I did not read past your headline "broken release ..." and I am 
> not obliged to.
> 
> 
> 
> > This is a prime example of "people will never learn not to do things like
> > thread hijacking, cross-posting, etc"...
> >
> > I'm open for constructive discussion on the original thread (which
> > for the record was "why do I have to run guix environment --ad-hoc guix"
> > in the SD installer on baremetal not in a VM"), I will ignore
> > this hijacked thread now. Please don't include me anymore in replies.
> > Thanks.


https://www.ietf.org/rfc/rfc1855.txt and common sense still applies in 2017.
Either make use of the mailinglist the correct way or don't use it at all.

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: The broken 0.13 release for GuixSD
  2017-05-24  7:59 The broken 0.13 release for GuixSD ng0
  2017-05-24  8:41 ` ng0
@ 2017-05-24 10:26 ` Ricardo Wurmus
  2017-05-24 11:27   ` ng0
  1 sibling, 1 reply; 16+ messages in thread
From: Ricardo Wurmus @ 2017-05-24 10:26 UTC (permalink / raw)
  To: ng0; +Cc: guix-devel


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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: The broken 0.13 release for GuixSD
  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
  0 siblings, 2 replies; 16+ messages in thread
From: ng0 @ 2017-05-24 11:27 UTC (permalink / raw)
  To: Ricardo Wurmus; +Cc: guix-devel

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.

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: The broken 0.13 release for GuixSD
  2017-05-24 11:27   ` ng0
@ 2017-05-24 11:32     ` Ricardo Wurmus
  2017-05-24 11:35     ` Fox
  1 sibling, 0 replies; 16+ messages in thread
From: Ricardo Wurmus @ 2017-05-24 11:32 UTC (permalink / raw)
  To: ng0; +Cc: guix-devel


>> 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 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=27034 and
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=27032 this.

Then it’s better to add additional information to these bug reports
instead of diluting the discussion by starting a new thread on
guix-devel.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

^ permalink raw reply	[flat|nested] 16+ messages in thread

* 0.13 release for GuixSD
  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
  1 sibling, 1 reply; 16+ messages in thread
From: Fox @ 2017-05-24 11:35 UTC (permalink / raw)
  To: guix-devel

as I typed in IRC, I encountered some test fail too earlier. Sorry I 
forgot how I got over it, maybe it was that install where I missed to 
submit one BASH LINE from the install manual (might have been fixed by 
now anyway).
Just to say that test failures do occur.

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: 0.13 release for GuixSD
  2017-05-24 11:35     ` Fox
@ 2017-05-24 11:59       ` Ludovic Courtès
  0 siblings, 0 replies; 16+ messages in thread
From: Ludovic Courtès @ 2017-05-24 11:59 UTC (permalink / raw)
  To: Fox; +Cc: guix-devel

Fox <firefox@firemail.cc> skribis:

> as I typed in IRC, I encountered some test fail too earlier. Sorry I
> forgot how I got over it, maybe it was that install where I missed to
> submit one BASH LINE from the install manual (might have been fixed by
> now anyway).
> Just to say that test failures do occur.

This is being worked on, please see <https://bugs.gnu.org/27032>.  You
can contribute to the discussion there by emailing
27032@debbugs.gnu.org.

Thanks in advance!

Ludo’.

^ permalink raw reply	[flat|nested] 16+ messages in thread

end of thread, other threads:[~2017-05-24 12:00 UTC | newest]

Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2017-05-24 11:32     ` Ricardo Wurmus
2017-05-24 11:35     ` Fox
2017-05-24 11:59       ` Ludovic Courtès

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