<cbaines>to be honest, it might be good to provide one for usability, so that you can just give it the "name" of an environment you've saved, and it does the rest
<lukas__>right that was my mental model while reading guix manual and found nothing. Might be cool if guix starts shell with environment variables inside container
<cbaines>You can do guix environment --container ... but I don't know an easy way of combining that with saving profiles
<cbaines>making that easy is probably a good reason to make this possible via a command
<Apteryx>ahah! I found out why starting geiser with dirty guix checkout is slow.
<Apteryx>it has nothing to do with emacs-guix; simply Geiser runs guile without the --no-auto-compile, and compilation takes that much time compared to simply evaluate the modified module (linux.scm -> 2m15s compared to 5.5s)
<ng0>that's an input of kdbus, and kdbus "… builds on top of QtDbus"
<cehteh>maybe we shall start a 'guixsd system administrators handbook' where details about system/daemon configuration is explained. the main manual getting alreadly considerably big
<Apteryx>tl;dr: If you even see "wrong-type-argument arrayp error" when using emacs-guix and don't want to bother going in your guix checkout to run make, configure the following: (setq guix-guile-program '("guile" "--no-auto-compile")) in your .emacs (https://notabug.org/alezost/emacs-guix/issues/2)
<elc79>cbaines, i did it to day and failed because of grub after a few hours
<elc79>i don't know why it recompiled grub because it's working well, i did guix system reconfigure for swap
<rekado_>elc79: you don’t need to run “guix pull” between “guix system reconfigure”
<elc79>i know, but anyway guix system reconfigure compiled grub and it failed
<rekado_>it won’t do this when you’re using the same version of Guix.
<elc79>i changed one line in my config.scm, then i did guix system reconfigure and it compiled many packages like qemu (i didn't installed this package) and after began to compile grub and it failed and guix system reconfigure was stopped
<rekado_>how do you run “guix system reconfigure”?
<rekado_>this sounds like you’re not using the same version as for your previous install.
<rekado_>elc79: this will run the current user’s “guix” but as root.
<elc79>rekado_: i did sudo without '-E' option, that was the problem?
<ng0>basically in WK words g13 replaces LUKS and works directly with dm-crypt. you can encrypt assymetric this way, use multiple keys and use smartcards like GNUk Token. But as I understand it, it is for experimentierfreudige people atm.
<cbaines>I believe its the only supported bootloader at the moment, so running guix system reconfigure necessitates a version of grub being installed
<cbaines>elc79, did you try adding berlin.guixsd.org as a substitutes server?
<cbaines>it could have a binary substitute for the grub version you're buiilding
<elc79>no, this server has the binaries for all packages??
<mekeor>elc79: if you have specified '(bootloader (grub-configuration …' in your system.scm, guix system reconfigure system.scm' will make sure the latest grub is installed into this new system-generation.
<elc79>i installed guix yesterday, i don't think grub made a new version today
<rekado_>elc79: you have to be sure about the version of guix you use
<rekado_>otherwise you’re just stumbling around in confusion
<rekado_>if you installed GuixSD yesterday and now guix tries to build grub from source then the version of Guix obviously differs between these two events.
<elc79>the version yesterday was 0.13, how can i check the version today?
<elc79>This is free software: you are free to change and redistribute it.
<elc79>There is NO WARRANTY, to the extent permitted by law.
<mekeor>well. how exactly do you run "guix system reconfigure"? – if you run it with "sudo", i think "guix --version" should give you the version of guix which is used for the reconfiguration. otherwise, if you run "guix system reconfigure" without "sudo", but as root-user, then you should run "guix --version" as root to find out the version of guix used to reconfigure, of course
<mekeor>elc79: well, this is strange. there's no version in the output?
<elc79>i'm going to this as root in tty2, not in the desktop terminal as sudo
<mekeor>elc79: you could also run "su" in the desktop terminal to log-in as root, btw
<ng0>have you run guix pull after installing the 0.13 tarball?
<civodul>Apteryx: 'origin' looks like the right thing if you want to add the above file as a udev rule
<civodul>the difficulty is that the udev machinery expects the file in a lib/udev subdir, not at the top-level
<civodul>so you'd have to write a 'computed-file' that simply copies the file in the right subdir
<Apteryx>Hi civodul! My idea was to use the configuration way that we already provides in the dorm of extending the rules field of th eudev-service-type. This field takes a list of udev-rule records. These records are formed by two things: a file name and the file content (as a string). E.g., if I give (udev-rules "51-android.rules" "content...") it will be placed for me under the lib/udev directory.
<Apteryx>I'm not sure how to do it. IIUC, origin is a dumb record. I cannot input it as a string.
<Apteryx>So I probably need the machinery to lower it as an entry to the store (download-to-store/add-to-store?) and then do some basic file reading operating to get it as a string... Or if you know of a simpler way :)