***svetlana__ is now known as svetlana
<sneek>davexunit, you have 1 message. <davexunit>I added an extra 512MB of RAM to the X60s and that solved the out of memory issue. <davexunit>however, it's still forcing a build of guix for some reason <davexunit>and a test fails in nar.scm so I'm stuck once again. <SideEffffECt>so I would like to ask, how is guix standing? how is it good at binary determinism? <svetlana>how do I copy a terminal output from qemu?; it gave more than one screenful, and i am unable to select, it does nothing when i try to click or right-click <civodul>svetlana: is the guest using the console or Xorg? <svetlana>I am running qemu in a gnome instance on the host OS. <civodul>yes, but i'm asking about the guest: is it in the console or in X? <svetlana>civodul, I don't know... it is a separate window with a cli session in it. <civodul>so what you can do is to run qemu with "-serial stdio" <civodul>and then, in the GRUB menu, add console=ttyS0 to the kernel command line <civodul>BTW, did you run qemu with "-m 1024" or similar? (the out-of-memory issues suggests that no) <svetlana>I did use -m 1024, yes; I only removed the -enable-kvm bit from the line the documentation mentioned: qemu-system-x86_64 -m 1024 -net nic,model=e1000 -net user gnu-system-demo-0.5.qcow2 <svetlana>If it's the random access memory, I think I should have some 4GiB ram and could double it if desired. <svetlana>I added the things like you said (serial and console) and am waiting for it to boot with 1024 memory atm. <svetlana>how do I copy and paste things now? selecting still does nothing, nor does right-clicking. <DusXMT>Is there any way of debugging the boot process of a system installed by guix? Does it keep any logs? (I checked /var/log and it's empty) ***DusXMT is now known as DusXMT_
<DusXMT>Ah, I found the issue. Apparently, something was wrong with my user definition, the system now boots properly <DusXMT>I think the problem was that the user's gid was set to 100, what the info file suggests. Changing it to 1000 gets rid of the error, and the system boots. <civodul>svetlana: with console=ttyS0 it should redirect console output to the host's stdout <civodul>that makes it easier to copy the output <svetlana>it does not, atm; will send you a grub screenshot in a minute <civodul>however, i think mingetty won't be running there <civodul>svetlana: on stdout, not in the qemu window <svetlana>yes, you mean it'd output stuff into host OS terminal instead of its own terminal <svetlana>linux /nix/store/.... --root=/dev/vda1/ ... --console-ttyS0 <svetlana>is that the correct syntax? you keep mentioning it without the two dashes <DusXMT>civodul: I don't have a clue, it scrolled off too quick, me only getting a kernel panic that init died <civodul>svetlana: no, literally: console=ttyS0 <svetlana>linux /nix/store/.... --root=/dev/vda1/ ... console-ttyS0 <svetlana>linux /nix/store/.... --root=/dev/vda1/ ... console=ttyS0 <civodul>DusXMT: what init is failing? the one of the installation image? the one of an installed system? <DusXMT>civodul: A system installed with "guix system init", the problem seems to have been that a user I defined had his main group set to "100", that's what was in the example on the info page <DusXMT>when I set it to "1000", it booted no problem <DusXMT>I called the command from a gNewSence setup on a different partition <civodul>i don't see that example in current master though <jmd>How do I specify to Guix that a binary must be installed setuid root? <DusXMT>civodul: It's in section 6.7.1 of the manual, that's what I used as my template. It seems outdated (for example, gid should be group, #:port should be #:port-number, etc) <Steap>How do I run a single test in Guix ? <jmd>Steap: I haven't tried it, but presumably "make check TESTSUITEFLAGS=<n> <DusXMT>davexunit: me, just got my setup working <jmd>davexunit: Sometimes. <svetlana>for some reason it still outputs the things from package manager into its own console, not the console on the host OS, so that I loose ability to read them (unless I perhaps send them to file on there) <svetlana>I'll have a look at qemu support means and return later <davexunit>on my thinkpad X60, I have a test failure in nar.scm <jmd>Haven't tried it recently. <DusXMT>davexunit: mine did, I tried today <davexunit>oh forgot a detail: this is the test suite for the 0.6 release. <Steap>jmd: not sure xactly of what flags I can pass <jmd>I think I did have several failures with 0.6 <Steap>I'd just love to run tests/packages.scm <DusXMT>davexunit: my run today was of the git, so maybe it's a big in 0.6 <davexunit>it's the reason that I can't install guix on my X60. <davexunit>perhaps I should edit the install image to use the latest development version. <davexunit>but maybe it is using the dev version... I don't know, it's all very confusing. <jmd>It's about time we had another release. <davexunit>I want to confirm that the install image works on i686 before the release. <jmd>Oh and you have to build guix under guix. <Steap>oh ok, make check TESTS=tests/packages.scm is enough *davexunit looks over guix.el <DusXMT>*sigh*... Looks like the guix system isn't crash-proof. Not good news for my half-broken netbook... <DusXMT>davexunit: It crashed, because of hardware issues, and now when I try to boot it, it gives me a kernel panic... ***jmd is now known as all
<civodul>DusXMT: yeah, apparently the faulty example is no longer in master <civodul>sneek: later tell see the 'setuid-programs' field of 'operating-system' <civodul>davexunit: we'll postpone the release until next week, i think <civodul>i'll be traveling to the Cauldron over the week end <civodul>davexunit: could you post the test-suite.log and nar.log? <davexunit>civodul: yeah, I'll try the build again tonight and get the logs. <civodul>DusXMT: this is terrible, could you try to gather more info, like what happens before the kernel panic? ***civodul changes topic to 'GNU Guix --- http://gnu.org/s/guix/ --- 0.7 is in the works: https://lists.gnu.org/archive/html/guix-devel/2014-05/msg00110.html --- testing needed: http://lists.gnu.org/archive/html/guix-devel/2014-06/msg00154.html --- come eat our dog food! :-)'
<DusXMT>civodul: the screen is too small, it scrolled off, only leaving me with "init died". I already reformatted and reinstanted the system, so unfortunately no. <davexunit>civodul: oh, neat. didn't know about it. all the cool GNU stuff happens in europe. <DusXMT>civodul: Hmm, I think I got the same problem again, and it doesn't seem hardware related <DusXMT>If I try to run any program, like `ls', I get "no such file or directrory", even if it exists <DusXMT>I bet if I reboot, I'll get the panic again <DusXMT>this happened the second time already, when trying to install man-db, during the operation, I get "/gnu/store/yadayadayada-guix-0.6.20b1d19/libexec/guix/substitute-binary': No such file or directory, and it starts misbehaving <DusXMT>yup, the same panic after reboot <mark_weaver>sneek: later tell jmd see the 'setuid-programs' field of 'operating-system'. <mark_weaver>civodul: when you send that to sneek, you left out the 'jmd', so if someone shows up with nick 'see', they'll get the message :) <mark_weaver>civodul: could you try contacting the Loongson 3A machine again? it had crashed, alas. back up now. <civodul>lemme try again contacting the build machine <civodul>alezost: just tried guix.el, works out of the box, and works great! <davexunit>that's great to hear. I want to try it out tonight. <waxysubs>civodul: you wrote: sneek: later tell see the 'setuid-programs' field of 'operating-system' <davexunit>I looked at the code and it is beautiful. people complain about elisp a lot, but it can be really elegant. <mark_weaver>civodul: that's good! hopefully things work properly now. <alezost>civodul: ok, great, could you confirm that pushing the "location" button in a "*Guix Package info*" buffer also works <civodul>alezost: it works, but the location is erroneous, which is weird <davexunit>guix.el is a very interesting use of geiser. I wonder if I could apply this technique to one of my other projects. <alezost>civodul: what package did you look for? <alezost>civodul: I've noticed that "package-location" function returns strange locations for some packages <civodul>but i think the location is correct at the Scheme level <mark_weaver>sneek: later tell civodul I think I fixed the problem on the build slave. can you try again? <jxself>Oh, FFmpeg finally supports WebVTT. *jxself goes about sending an update for Guix <jxself>Yep, in their version 2.3 which was released today. <davexunit>it's pretty neat to be able to make a quick patch and have guix up-to-date with upstream releases. :) <jxself>Yes although I'm taking the time to compile it myself first and make sure everything's good. <SideEffffECt>so I would like to ask, how is guix standing? how is it good at binary determinism? 
