IRC channel logs
2014-07-04.log
back to list of logs
<Fulax>how large is the current filesystem? <civodul>we'll have to get better hosting for the front-end <sveta>how do I verify signature? downloaded the qcow2.xz, but tar -xf whines that it's not a sane archive *sveta downloaded the qcow2.xz.sig, but doesn't know what to do with it <zerwas>sveta: Sorry, don't know if you got it: You can check the signature with: gpg --verify gnu-system-demo-0.6.qcow2.xz.sig <zerwas>And you can extract the file with "unxz" <zerwas>I forgot that you first need to tell gpg civodul's public key with gpg --recv-keys EA52ECF4 <zerwas>Then the verify command should tell you something along the lines of "Good signature from Ludovic" <sveta>it is a nice tool. it tells me about bad signature, and I will re-download. <alezost>hi, I sent a message to guix-devel@gnu.org but it looks like it was lost in the way, so I ask here as well. I've tried to build guix from git, but "make check" failed on "smalltalk" with this backtrace: http://paste.debian.net/108123 <alezost>Is it normal? I mean does it fail for other people? <sveta>I've got the download properly and the signature verifies, but tar still thinks this does not look like a tar archive. <zerwas>sveta: That's because you need the tool "unxz" :) <zerwas>In debian-based distributions it can be found in the package "xz-utils" <sveta>I did get the 0.5 version, even though the documentation mentions 0.6 (and you do too). why - dunno. -- unxz is installed and I am not continuing <sveta>I appear to have kvm support disabled in the BIOS. should I go enable it or is there another way to run this in a virtualbox? <civodul>sveta: you can run it in QEMU without "-enable-kvm"; it will just be slower <civodul>alezost: the first post takes a while to get through <civodul>alezost: i can reproduce the error now <civodul>alezost: you can try git pull && make now <sveta>yes, it mentioned about unpacking or parsing it during boot (no error, but it's a new term to me) <sveta>also, qemu took over the mouse and I couldn't do a thing and had to kill it off. <civodul>use ctrl+alt to regain mouse control from QEMU <sveta>"decompressing Linux ... parsing ELF ..." <alezost>civodul: i see your commit, thank you; I suspected that it should be some little modification :) <civodul>Aurel looks neat, and i've been hoping to have something similar for Guix <civodul>so if you're willing to port it, i'm happy to offer you a beer or something ;-) <alezost>civodul: I actually had that idea as well when I learnt about guix. The main thing is: how to get info about the packages. For aurel I just used json info returned by the AUR server. <alezost>For guix it would probably be better to use a connection to guile (perhaps with some geiser functionality) than to parse shell output from "guix package" commands <sveta>aw, i tried to install icecat at the thing but it gave me a lovely error (and I can't scroll the window or copy it); i need to do some more reading i guess and expect less <alezost>ouch, after "make check" I had: TOTAL: 31 PASS: 17 FAIL: 14. Also it says "Please report to bug-guix@gnu.org". I'm not sure I did everything right. Should I report? <civodul>alezost: could you check tests/store.log for something obvious, like "socket name too long"? <civodul>could you paste all of test-suite.log? <civodul>alezost: can you try "rm gnu/packages/bootstrap/i686*/* && make && make check TESTS=tests/derivations.scm"? <civodul>alezost: re Aurel, it could be Geiser or just get the output of "guix package --list-available" and the like <alezost>failed on make after deleting bootstrap files: "No rule to make target 'gnu/packages/bootstrap/i686-linux/bash', needed by 'all-am'. Stop." <alezost>civodul: thanks for the link, actually I'm very interested in Emacs UI for guix <civodul>oops, can you restore that file from git? <alezost>yes, well "make" just downloaded guile-2.0.9 and "make check TESTS=tests/derivations.scm" failed <alezost>civodul: is that guy (Yagnesh Raghava Yakkala) working on guix.el? <civodul>alezost: no, he gave up before the GSoC deadline, and hasn't actually done anything <civodul>alezost: could you paste tests/derivations.log and derivations.log again? <alezost>I don't have derivations.log, just derivations.scm <civodul>alezost: can you post test-suite.log to bug-guix@gnu.org so we keep track of that? <civodul>and we'll keep discussing from there <civodul>i'm on x86_64, but i think a few people are on i686 <alezost>civodul: ok, I have sent the message <alezost>as for guix.el, I have a wish to dive into it (after I install guix and play with it for some time) <jmd>as it happens, right now, I am, yes. <jmd>But sometimes on mips <ph4n70m4s>Munich Germany ? Let me check the air tickets :-D <civodul>make sure to register too: it's gratis but it helps jmd & co. organize things <taylanub>is it a bug that when I pass '-p ~/.guix-profile' to 'guix package', it creates ~/.guix-profile-1-link, ~/.guix-profile-2-link, etc.? I suppose it isn't, I'd need to pass '-p /var/guix/profiles/per-user/tub/guix-profile' instead, to which ~/.guix-profile is just a symlink and guix "doesn't know" about this additional indirection... <taylanub>this solves mystery 1, which is why I ended up having those files. mystery 2 is why my guix insists on using /var/guix/profiles/default if I don't pass -p <Mathnerd314>does Guix have a way to pretty-print a (raw/primitive) derivation? <Mathnerd314>the standard pretty-print doesn't show newlines, which means things like bash scripts are unreadable <civodul>Mathnerd314: you mean pretty-print the contents of a .drv file? <civodul>then no, it doesn't have any special support for that <civodul>taylanub: i'd say it's not really a bug, but perhaps it could be improved still :-) <civodul>do you want to report that to bug-guix, mentioning what you'd expect to happen? <Mathnerd314>hm, ok. so far cat file | bglpp | sed 's/\\\\n/\\n/g' | less has been sufficient, but it would be nice to have a specialized tool <taylanub>hrm, I'll report it, though not sure what Guix could even do. follow all symlinks except the last two maybe? :P we'll see <civodul>Mathnerd314: the API in (guix derivations) has stuff to help, but it depends on what info you'd like to extract <civodul>taylanub: yeah, dunno, haven't given much thought about it :-) <Mathnerd314>civodul: I just want a pretty-printer, I'm working with nixpkgs so there's not much info to extract from the shell scripts