<ryuslash>after changing /etc/config.scm, what's the easiest way (or best way) to have those changes take effect? <mark_weaver>ryuslash: run "guix system reconfigure /etc/config.scm" as root <ryuslash>mark_weaver: thanks, that's what I'm doing right now. was afraid it might have been the wrong choice :) it's taking awhile <ryuslash>mark_weaver: do you know if a package or user can install custom keyboard layouts now? I think we looked into it a few months ago. <ryuslash>well at least I can still use normal colemak :) that helps :P <ryuslash>should I define my keyboard layout in /etc/X11/xorg.conf.d/ somewhere or does guix have a special way of configuring it? <mark_weaver>we should have a better answer for custom keymaps, but that is best discussed on guix-devel@gnu.org. <mark_weaver>but I'm not sure if that's sufficient to do what you want. <ryuslash>for now I just need to set XkbLayout and XkbVariant <mark_weaver>sorry, my knowledge of this area of X configuration is weak and I don't have time at the moment to research it. <ryuslash>that's ok, thanks for the pointers, I'm trying to read the commit right now. <ryuslash>assuming I've correctly added a mapped-device to my /etc/config.scm, and I've run `guix system reconfigure /etc/config.scm', do I need to restart to see any changes or is there some other way to tell if it's worked? I expected to have been asked for a password to unlock it or at least see an /etc/crypttab appear, but neither has happened. Although there is a high probability that I misunderstood the way it's supposed to work. <mark_weaver>ryuslash: at present, reboots are needed after 'guix system reconfigure' to update services. we intend to remove that limitation at some point. <ryuslash>mark_weaver: thanks. I thought it might not be necessary since the info document states that the new configuration gets switched to <mark_weaver>the /run/current-system symlink is changed immediately, so programs installed in the system profile are immediately available. but at present our init daemon still keeps all the old services. *zacts is going to try guix pm armhf on top of debian jessie beaglebone black <zacts>(which will be awesome, because I'll be able to use up-to-date packages once jessie gets stale) <mark_weaver>zacts: unfortunately, we don't yet have any binary substitutes available, so you'll have to bootstrap the entire system including compilers, etc. I doubt the BBB is powerful enough to do that. <zacts>mark_weaver: GNU Guix 0.8.2 Binary (armhf) <mark_weaver>I'm not sure it has enough RAM, and even if it was possible it would probably take a very long time, maybe more than a week. <zacts>^ is this not a binary setup of armhf? <mark_weaver>it contains a binary of the 'guix' package (and the other packages referenced from it), but that's it <mark_weaver>i.e. the minimal amount to allow you to run the 'guix' command and deamon. <mark_weaver>what we need to rectify this unfortunate situation is a dedicated armhf build slave for Hydra. <mark_weaver>at present, guix armhf users need a sufficiently powerful machine to build everything from source code. <zacts>oh, so I would just be building my own arm packages <zacts>so one idea would be to do this in armhf qemu on an x86_64 host <zacts>and then copy the binaries that way <zacts>^ Linaro has qemu versions specifically targetting my beaglebone <mark_weaver>I have one concern about that approach: qemu is designed to run correct code as quickly as possible. it does not guarantee that everything that would fail on the real target will fail in qemu. <zacts>perhaps if it works, you could setup a qemu instance for armhf, and then note that the packages are not tested on real hw <mark_weaver>meanwhile, autoconf, and some other software, does experiments to see what works and what doesn't. <zacts>so an (unofficial) package repo for armhf, until you get dedicated hw <mark_weaver>I don't want to build a bunch of stuff that might have various hard-to-find problems, and if we put a temporary solution in place that might well kill any motivation to get a real build slave for armhf. <ryuslash>time to go, bye everyone. thanks for helping again mark_weaver <davexunit>I spent a good portion of my day setting up my guixsd laptop. things are starting to get sane. <davexunit>dotfiles synced, profile version controlled. <davexunit>working on my emacs config so that it doesn't throw errors when I'm missing packages. <sirgazil>Does GuixSD modify language-specific package managers to avoid installing non-free packages? <davexunit>guixsd doesn't promote non-free software, so I don't think that's an issue. ***exio4 is now known as init
<rekado>hmm, I no longer remember my passphrase for my SSH keys ... Under GNOME seahorse managed them. Got to figure out how to unlock them. <rekado>(I knew this would bite me one fine day. <toothbrush0>rekado: better than forgetting your gpg keyphrases :/ *toothbrush0 obviously would *never* do such a thing <rekado>woo, found an encrypted note with the passphrases. Forgetting my gpg passphrases would be disastrous. <toothbrush0>rekado: i sometimes wonder how to handle data security if my "threat" model involves amnesia :p <mthl>civodul: would you like me to make the licence notifications for the website? <civodul>mthl: yes, that would be nice of you! <civodul>basically there are two or three copyright lines per file, plus something like "Initially written by Felipe [...] who waives all copyright interest on this file." <civodul>and a link to the Git repo browser in the footer <civodul>ph4nt0mas: ok ok, i'll reply to your message <civodul>sorry for the delay, don't panic ;-) <ph4nt0mas>I am checking all the dependencies, it's using the right glibc <ph4nt0mas>all the previous packages are built like expected <rekado>paroneayea: does guile-emacs actually work for you? I cannot even start it without this error: "Cannot open load file: No such file or directory, emacs-lisp/byte-run" <mark_weaver>rekado: I see the same problem. running "emacs -Q" works though. <paroneayea>I do have to stop it from loading my whole .emacs <rekado>hmm, I also use "emacs -q". It works with -Q, though. <rekado>startup is *very* slow, though. (Is it compiling the el files on first start?) <taylanub>rekado: I think it's not compiling them, but loading them all from source just takes so much time <alezost>espectalll123: hello, you may just ask <espectalll123>Everything went OK – but, my bad, Guix tried to install GRUB on /dev/sdX <espectalll123>Path `/boot/grub' is not readable by GRUB on boot. Installation is impossible. Aborting. <espectalll123>Then I did chroot, but I'm unable to find the GRUB binaries' path, as it gets quite hard to browse /gnu/store <mark_weaver>because of the way guix works, more arguments are needed to grub-install <mark_weaver>I might be able to dig up the command, if you give me a few minutes <mark_weaver>the robot answer would be "wipe the target partition and re-run 'guix system init'." <mark_weaver>but it happens, I seem to recall the grub-install was the last thing done by 'guix system init', and it may be easy to redo that step manually. <mark_weaver>supporting the unusual features we provide requires that most things cannot be in fixed standard places on the filesystem. <mark_weaver>we effectively support having many different systems on the same partition, and so 'grub-install' without a store path cannot know which of those systems you wish to boot into, which grub to use, etc. <mark_weaver>and that's why it can't be as simple as it is for other distros <espectalll123>That also would allow to install a full Guix OS inside another distro, right? <mark_weaver>there are tradeoffs. if you don't like that one, you probably won't like guix. <mark_weaver>the packages in Guix, yes, but not GuixSD itself, because although *almost* everything is in /gnu/store on GuixSD, there are actually a few other directories it needs, notably /etc <mark_weaver>much of what's in /etc on guixsd are symlinks into the store, but still this GuixSD /etc can't co-exist with the /etc from a standard system. <paroneayea>wait, how would unionfs deal with symlinks? I don't even know :) *paroneayea isn't serious anyway <mark_weaver>espectalll123: okay, the command it runs is actually just: grub-install --no-floppy --boot-directory <mount-point>/boot /dev/sd<??> <mark_weaver>I should double-check that it doesn't do anything after installing grub. <mark_weaver>a GC root, which protects some of the resources needed by the grub.cfg from garbage collection, is renamed <mark_weaver>I guess it's /var/guix/gcroots/grub.cfg.new which should be renamed to remove that ".new" suffix. <mark_weaver>espectalll123: see section 6.2.6 (Locales) in the Guix manual. <mark_weaver>oooh, XFCE on GuixSD seems to handle multiple monitors much better than it did when I last checked. ***jchmrt is now known as Guest67731
<zacts>how long does the following command usually take on your machines? # /root/.guix-profile/bin/guix-daemon --build-users-group=guix-builder <zacts>(for some reason I thought it was a command to auto groupadd and useradd