<civodul>nckx: i'm polishing the UUID thing :-) <ng0>In my VM it seems like it differs. A second opinion would be good, then double checking if some of the other switches are affected by that and will no longer be needed. Then the creation of a patch to drop them. I consider customized variants easy to be produced, but maybe we should have an "tor/hardened"? But if we just drop -expensive-hardening there is still some hardening. <nckx>civodul: Sorry it took me a while to catch on to what's computed when. I've only started to peek into the world on the other side of gexps last week. Should have started sooner — it's not *that* scary. <nckx>civodul: I'm excessively prone to impostor syndrome as soon as something even approaches the ‘S’ in CS. <nckx>But the word ‘monad’ still makes me nervous. <civodul>i've been trying to overcome it, not always successfully <nckx>civodul: well, that certainly puts things in perspective. :-) <ng0>yes, I'm convinced. I think the tor change is good. <ng0>sending the email in a momnt <nckx>Ugh. Timeout exceeded while building tor. Let's try again. <buenouanq>Stock Gnome on GuixSD, some of my windows won't tile like they're supposed to and I can't figure out why. <buenouanq>I have keyboard shortcuts for `View split on left/right' that work for most things - But some (Nautilus, Transmission, GIMP) just ignore it, it's quite frustrating. <buenouanq>They actually will do it on my larger monitor though - Is there some sort silly size constraint on this? And why would it only be some programs and not all? <buenouanq>Anyone have any ideas about this? Is it a Gnome thing or a GuixSD thing? <buenouanq>Perhaps a GTK thing for each of these individual programs? <nckx>sneek: later tell jonsger Congratulations! May there be many more. <efraim>i'm currently working on updating the hikey's firmware to see if I can get the debian netboot installer running (known to work) before I test my aarch64 guixsd image <efraim>debian's instruction are "update the firmware from modified u-boot to uefi and run the netinstaller" <efraim>i just realized the board doesn't have ethernet <civodul>efraim: BTW, what about writing a blog entry about the aarch64 port? <rekado_>civodul: the servers are accessible now. But … the firewall blocks outgoing HTTP, so I can’t use Guix yet :) <civodul>efraim: i think you left that question unanswered before :-) <civodul>rekado_: woohoo! great progress anyway, thanks a lot! <rekado_>I also don’t have git access, so I’ll just copy over the contents of the maintenance repo. <efraim>rekado_ civodul: I'll try to today, hacking on it is just more exciting :) <civodul>rekado_: i guess you could make an SSH tunnel or something <jonsger>how to upgrade guix when build from git? <sneek>Welcome back jonsger, you have 1 message. <sneek>jonsger, nckx says: Congratulations! May there be many more. <oriansj>wigust: if I remember correctly the majority of guix users don't use guixsd simply because the software they consider essential hasn't been packaged yet or because guixsd is still considered beta software at this point <dTal>I don't use it ever since I tried to change my hostname and ended up recompiling Samba <jonsger>oriansj: and they have "problems" with linux-libre <buenouanq>everything else seems crippled and unusably inadequate to me now <oriansj>jonsger: that usually simply means hardware without good drivers <jonsger>I didn't get guixsd run inside qemu so I decided to use just guix <oriansj>buenouanq: some come for the ease of development, some for the reproducibility and some for the enpowerment of users <buenouanq>Freedom is more important than capability, comfort, and convenience. <buenouanq>Luckily, with GuixSD, I can finally have it all. <oriansj>buenouanq: freedom without community isn't freedom for long <oriansj>personally I use guix because it gives me a far easier target for my bootstrap project <oriansj>basically reducing the guix bootstrap binaries down to a hex assembler and an exec_enable both less than 500 bytes <oriansj>which then are used to make a macro assembler, then a lisp and forth and finally a C compiler which can bootstrap guile <oriansj>also I am making sure the bootstrap pieces are universally reproducible (aka one could use a c64 to verify everything) <wigust>jonsger: on guixsd we have a symlink ~/.config/guix/latest to /gnu/store/...-guix-latest which you can point to git checkout if you want to. May be something similiar on guix for other distroes. <rekado_>I’m not using lsh often enough to remember what key I provided for the build farm. <rekado_>I remember that I converted an OpenSSH key… <rekado_>Is anyone else using multiple SSH keys? Is this a good idea or should I just give up and use the same key everywhere? <rekado_>ACTION configures the bayfront clone to be like bayfront <lfam>rekado_: I use per-host SSH keys, give them descriptive names, and use ~/.ssh/config to make them easy to use <lfam>rekado_: No, just openssh <rekado_>guix system reconfigure --fallback /etc/config.scm <rekado_><unknown location>: error: source expression failed to match any pattern <civodul>rekado_: seriously though, once you've found which macro use was causing this, please report it; we could probably hack something to improve it <civodul>until we have 'syntax-parse', that is <rekado_>I think it’s because I changed “local-file” to “maintenance-file” inside a gexp <civodul>lfam: looks like you can go ahead and ask for a "guix" vendor zone <rekado_>maintenance-file is a procedure that prefixes the file name and returns local-file. <civodul>rekado_: that'd be an unbound variable, not a syntax error no? <lfam>civodul: Great, I'll apply for it today <rekado_>so I ripped it out and manually changed the file name arguments to local-file <civodul>lfam: notice this pattern typical of GNU, BTW ;-) <civodul>rekado_: 'local-file' is a macro, so perhaps you were passing it an incorrect number of arguments or something? <rekado_>I did (apply local-file (string-append …) args) <lfam>civodul: Which pattern, exactly? :) <rekado_>(define maintenance-file (name . args) …) <rekado_>erm (define (maintenance-file name . args) …) <rekado_>civodul: has there actually been a reply to your mail about NTP pool vendor zones? <lfam>Yes, it was recommended we apply for a 'guix' zone <efraim>lfam: just a quick here and out again, did you forget to remove the pcre patch or is it in use by something else? <lfam>efraim: Err, most likely my mistake :/ <lfam>Thanks for the many layers of review, everyone :) <rekado_>oh, *there* is the email! I’ve been having some problems with my mail lately :-/ <civodul>rekado_: (apply local-file ...) doesn't work indeed, should fix it ***Piece_Maker is now known as Acou_Bass
<efraim>how do I take a guix substitute key and add it to bayfront's %guix-daemon-config that I copied? <jlicht>hello #guix! Is anyone else running into a parser error when running `guix package -s tex' on current master? <rekado_>texinfo.scm:966:36: Throw to key `parser-error' with args `(#f "Unknown command" body)'. <jlicht>rekado_: np, thank /you/ for fixing it <jlicht>rekado_: that was quick, let me check ;-) <jlicht>rekado_: still getting: texinfo.scm:745:27: texinfo.scm:745:27: Throw to key `parser-error' with args `(#<input: string 26069a0> "EOF while reading a token " "reading char data")'. <jlicht>rekado_: issues like these should probably not really be killing guix, right? We are talking about the description fields of some packages afaik? <rekado_>yes, I think these errors should be caught. <jlicht>I can verify that the problem is fixed for now :-) <civodul>rekado_: "guix lint -c description,synopsis" catches it (among other things) <rekado_>I reran “guix lint” just now; must have forgotten that at the time <jlicht>civodul: I know it has been talked about on the ML, but maybe there can be a (semi-automated) grace period for non-security related patches? <jlicht>and people who run guix from git (or set a certain flag) will make use of the system as it is now, but a "normal" user would only see these patches after e.g. 48 hours <davexunit>ACTION reads the target features for 0.13.1 and is excited <davexunit>does the new bootloader api mean that guixsd on arm can finally be a thing? <jlicht>davexunit: where can you read all this exciting news/ <buenouanq>I absolutely must get this running on my EOMA68. Whenever they actually ship finally (;-___-) <davexunit>jlicht: was looking at mailing list posts from awhile ago <jlicht>davexunit: yeah, me too. But it's good to know I have some fun stuff to look forward to reading then :D <civodul>jlicht: automation would be great indeed, but nobody is working on it AFAIK <efraim>How would system rollback work with u-boot? Unless we chained u-boot to grub <davexunit>u-boot doesn't support multiple boot targets? <efraim>I don't know, I always assumed it could boot just 1 target <ryanwatkins>Hey guys, I keep getting a very weird issues with package installations in GuixSD now, I am getting "profile contains conflicting entries for X:out"... any way to solve this? ***Guest46285 is now known as sturm
<amz3`>ryanwatkins: I think it's expected <az`>something wrong with my <M-x>guix - there is no any output and its freeze until I <C-g> <az`>now I do `guix package --fallback -u` and try again... but, any thoughts maybe? <lfam>az`: I'm not an Emacs user so I can't help you with that but, if nobody else responds here, I recommend asking for help on <help-guix@gnu.org> <wigust>az`: Hello. As I think, Emacs starts Guile REPL and Guix REPL which may need to compile missing things. <wigust>But it should work without latency after using Guix for sometime.