<brendyn>rekado: Dunno, I have all the M-x Guix… commands so guix.el must be loaded? I open a Scheme file in my git repo of Guix, press ! to run all the Emacs config stuff. I type M-x run-geiser. guix-devel-mode is supposed to be on since I'm in a Scheme file, but it isn't for some reason. I load it with M-x guix-devel-mode.
<brendyn>Testing C-c . l at a package definiton. I get ERROR: no code for module (guix monad-repl)
<brendyn>But also, that seems to be from a different REPL, then one I got with run-geiser isn't doing anything
<brendyn>Then I end up with 3 REPLs, two guile 2.2 and one internal guile 2.0.14
<Petter>I ran indent-code.el on my package recipe, now guix lint turned red with way too long lines. Did indent-code.el go a little overboard or should I just add a lot of newlines everywhere? http://sprunge.us/dLOW
<alezost>Petter: I think I know what happened: you need to be in the top dir of the guix tree and run it like this: "./etc/indent-code.el <your-file.scm>" (as it is mentioned in the manual), otherwise it won't work. I think I know how to fix this limitation.
<brendyn>I see, so after I setup a pure environment, running emacs goes to town on my enviroment reseting PATH and stuff like that
<janneke>wingo: on potluck...would my phantomjs patch set be a good candidate for potluck?
<wingo>janneke: i don't know. what's your phantomjs patch?
<janneke>the paches need some work that i'm not going to do right now
<alezost>brendyn: so that's the problem - guix is still compiled with Guile 2.0
<alezost>and when you try to use guix modules with guile 2.2, the new guile compiles them
<alezost>I mean, when you do "make", guix is build with guile 2.0, so you can use guix modules without problems, as they are compiled. But when you use guix modules with guile 2.0, the modules are compiled again for another guile version
<brendyn>This may explain a significan number of my problems.
<CcxWrk>Reading Guix and Nix docs, I'm seeing that Nix packages are described as functions taking configuration options, whereas Guix talks of G-Expressions. Should I conclude that in Guix it's impossible to pass in such configuration options besides of creating new package/expression?
<davexunit>CcxWrk: a package in guix is a first class Scheme object and you can manipulate them to make variants of them as you wish
<CcxWrk>Can you give an example? Say, I want to switch TLS implementation from openssl to gnutls or vice versa.
<davexunit>I don't have an example in front of me, but the guix source is full of such things.
<davexunit>you can make a new package that "inherits" from another and then change some fields
<davexunit>remember: packages are just plain Scheme objects
<davexunit>almost all of them are assigned to variables within various modules
<davexunit>so you import the modules you want, and reference the variables that contain the package objects
<brendyn>Yeah, Goldendict has the feature to search a directory, but I'll need to have that set so it's goes to the place where the dictionaries are installed
<CcxWrk>In my eyes that's just changing how package-1.0 gets resolved into different longhash-package-1.0 due to different options, it can do the very same as the commandline option. Just by means of matching some pattern of the package definitions.
<brendyn>kyamashita: Yeah something to do with vector math stuff
<apteryx[m]>amz3`: I have the same problem! I think the Guix binary downloaded over Guix pull puts it under /usr/local/etc/guix/acl. That'd be a bug I guess!
<lfam>apteryx[m]: Update root's copy of Guix, update the installed Guix package, and restart the daemon (`guix pull && guix package -u guix && $service-manager restart guix-daemon`)
<lfam>apteryx[m]: Regarding '/usr/local/etc/guix/acl', are you using Guix from a Git checkout? That path is the default value of $localstatedir; it's why our instructions suggest building Guix with './configure --localstatedir=/var'
<apteryx[m]>lfam: It might have been at some point but I've now fixed it. I'll try restarting the daemon
***kelsoo1 is now known as kelsoo
<apteryx[m]>lfam: thanks. I'm usually on GuixSD where I only need to reconfigure the system so I keep forgetting about how it works on a foreign distro!
<lfam>apteryx[m]: I understand :) And the story on a foreign distro, where root's copy of Guix is available system-wide in /usr/local/bin is a bit strange and easy to forget about! Especially since your user also has a Guix at ~/.config/guix/latest
<apteryx[m]>lfam: even after running ./configure --localstatedir=/var --sysconfdir=/etc in my git checkout, and doing 'sudo -s; guix pull; guix package -u guix --fallback; restart guix-daemon&, 'guix archive --authorize < bayfront.guixsd.org.pub' still only writes to /usr/local/etc/guix/acl :/
<janneke>amz3`: i tried to pick today to convert two boxes from +guix to GuixSD...bad timing
<brendyn>Hmm, so we have individual files for the likes of inkscape
<rekado>apteryx[m]: you may need to set “--prefix=/”
<rekado>I’m bisecting to figure out the cause of the substitute error
<nckx>paroneayea: Hm, maybe this isn't the same bug after all. I'm having trouble reproducing it myself (doesn't help that I'm working from a different checkout...)
<rekado>git bisect gives me a really harmless commit as the culprit.
<rekado>so maybe it’s not a problem with the code but with the substitute server
<rekado>(it’s a problem that the code crashes when a substitute server fails, of course)
<apteryx[m]>rekado: still no way; as 'sudo -s; guix archive --authorize < bayfront.guixsd.org.pub'. If I use my git checkout guix though, as a simple user, I get: ...permission denied: "/etc/guix/acl" so at least as my user it is OK.
<apteryx[m]>Where/how is the system guix loading (guix config) ?