IRC channel logs


back to list of logs

<civodul>excellent :-)
<sir123>Hey guys, I managed to have a successful install :) I used /dev/sda3 as the partition it was looking for, now it works great. My only issue is how to install programs in the new system. How do I use the USB environment to install programs in the new system in my non-privileged user? Cow-store doesn't link the program to the profile, or under /bin. Does anyone have any ideas? It seems the only program in the system is sh under /bi
<davexunit>sir123: why not install programs as your user from the booted system?
<jxself>And you won't find them in /bin.
<sir123>Because I can't use wpa-supplicant to connect to the web in the booted system.
<sir123>Once I have wpa-supplicant, I can load all the programs I need.
<davexunit>sir123: why not specify wpa-supplicant in the packages list of your config?
<davexunit>that way you have it on the booted system
<sir123>That's a good idea. I'll do that. Thank you
<davexunit>note that it will be a package available system-wide, not one installed to a per-user profile.
<davexunit>but for something like wpa-supplicant, I think that makes sense.
<mark_weaver>sir123: btw, we also have a (wicd-service) now, which you might prefer.
<sir123>That's fine. Btw, is there a way to specify user password in config? Saves time later.
<davexunit>sir123: user accounts have a field for the crypted password hash
<mark_weaver>sir123: see section 6.2.5 of the manual (User Accounts)
<mark_weaver>or you can just log in as root and set the password using "passwd <username>"
<sir123>I'll look into it. Thanks guys for all of your hard work in developing this system, and helping me. I really appreciate it.
<mark_weaver>sir123: you're welcome, I'm glad you got it working and had the patience to work through the problems. welcome to our community :)
<sir123>It's a privilege :)
<mark_weaver>sir123: btw, are you using a GPT partition table?
<mark_weaver>okay. I wonder if that's related to the fact that specifying the label didn't work.
<mark_weaver>I think most of us are using MSDOS partition tables, but I would also like to switch to GPT. just haven't gotten around to it yet.
<sir123>Might be. I think I'll grab the source and play around in a vm. See if I can replicate the issue and find the problem.
<mark_weaver>sir123: do you see a symlink for "root -> ../../sda3" in the output of "ls -l /dev/disk/by-label" ?
<ewemoa>sir123: congrats on your successful installation :)
<sir123>I have to go now, I'll try it when I get a chance.
<mark_weaver>sir123: we might be missing a kernel module in our initramfs.
<mark_weaver>sir123: okay, happy hacking!
<sir123>I'll see what I can find and report back.
*mark_weaver just realized that "GPT partition table" is terribly redundant :)
<jxself>It just means GPT has become a word in itself.
<mark_weaver>indeed :)
<mark_weaver>a bit like "ATM machine"
<davexunit>does someone have an extra NIC card I could borrow?
<ewemoa>"GPT" is a bit like "GNU
<mark_weaver>davexunit: I don't, but "NIC card" is too vague to know what you're looking for exactly. wired or wireless? what kind of interface? (USB, miniPCIe, ??)
<davexunit>I was just joining in on the redundant jokes.
<mark_weaver>ah, right. duh :)
<davexunit>I don't actually need a NIC.
<davexunit>or rather, a network interface card card.
<davexunit>I had a feeling my redundancy may have went undetected.
*mark_weaver can be a bit slow sometimes with jokes :-/
*ijp diagnoses RAS Syndrome
<davexunit>looked up RAS Syndrome on Wikipedia and found "pleonasm" that I'm very guilty of: PDF format
<davexunit>portable document format format
<mark_weaver>davexunit: I never thought of that one :)
<davexunit>me either!
<zacts>mark_weaver: do you think that guix 8.1 is good enough to where I can do an OpenSSH + irssi or emacs erc server?
<zacts>I only need OpenSSH / nftables or iptables / irssi or emacs / tmux
<davexunit>forgot a "0." ;)
<zacts>if that's the case, I'll try guix on my home server
<zacts>well, I guess I could just try, I don't know why I'm asking
<zacts>I mean I have nothing to lose
<jgrant>zacts: Certainly.
<jgrant>I was running GSD on my main computer for a week without any real issue, sans not having Stumpwm ready.
<jgrant>Personally, I'm apt to side to the side of Emacs for near everything -- but mosh/openssh and irssi should not be an issue either.
<davexunit>oh cool, we have mosh packaged.
<jgrant>Yeah, not sure when that happened but was playing with it when GSD was on my main box.
<jgrant>Now my main-box is hooked up to my rigged-together treadmill desk (on Parabola), and I have a dedicated Devel-laptop until I get Stumpwm and a few others done.
<jgrant>Whatever happened to Scrot?
<jgrant>That was in the repos for a bit and is seemingly not anymore.
<davexunit>it's packaged.
<jgrant>Ah it got moved, so my config didn't work for it.
<jgrant>From scrot.scm -> xdisorg.scm
<jgrant>I have about half of the depends for rtorrent, I need tok finish up on soon.
<davexunit>isn't that already packaged?
<jgrant>Hm, when did that happen?
<jgrant>Late November it seems.
<jgrant>Okay, one more thing to nix from the list. :^)
<jgrant>Sadly the two one's I really want/need to move over to GSD on all my boxes are big undertakings (Kodi & Stumpwm (and all the Clisp related depends that go with it)).
<jgrant>Well anyways, bed time. o/
<mark_weaver>zacts: we have emacs, openssh, and erc (which comes with emacs)
<mark_weaver>zacts: and we have irssi too, i see.
<mark_weaver>here's our package list:
<zacts>yeah, as I said, I don't know why I asked here. I can just do it myself
<zacts>I guess it was just an expression of the joy of the idea of using guix in production
<mark_weaver>I've been using it as my primary system for many months
<sir123>Hey, I'm back. After looking at, I inserted code to load wpa-supplicant: (gnu packages wpa-supplicant) ... (packages (cons wpa-supplicant %base-packages)). However, an init complains about 'no code for module (gnu packages wpa-supplicant). Obviously wpa-supplicant isn't a GNU package, but how would I modify the file to load it?
<davexunit>sir123: 'guix package -A wpa-supplicant' will tell you what module it's in
<sir123>Okay, it says gnu/packages/admin.scm:679:2.
<davexunit>there you go.
<sir123>So input that exactly?
<davexunit>use the module notation
<davexunit>(gnu packages admin)
<sir123>Perfect! Building now
<davexunit>(gnu packages <x>) is the module namespace for guix packages
<sir123>Okay, thanks.
<davexunit>guile transforms that into a file name and looks for it on the load path
<sir123>I noticed there wasn't a man page for guix. Should we start working on that?
<davexunit>sir123: there's an info manual.
<sir123>Oh, okay. Online?
<davexunit>we write documentation to be used with info readers, not man.
<davexunit>you just linked to the online HTML version, but the documentation is available in info format on your system.
<sir123>Oh. I need to learn the GNU infrastructure...
<davexunit>it's particularly convenient to read with emacs' info reader
<sir123>Ok. Might I ask how I could help the project now I have a working system?
<davexunit>packaging software that is useful to you is a good way
<sir123>Ok. I think I might start with libreoffice, if that's okay.
<sir123>Productivity isn't first goal, though. Do we have a page for package requests?
<davexunit>sir123: libreoffice is a WIP
<davexunit>it's a very large piece of software that is difficult to get working, too.
<davexunit>so I recommend finding a smaller package to start with.
<sir123>Yeah, I can understand that.
<davexunit>sir123: we have a wishlist
<davexunit>try to find something small, this list seems to be mostly large packages right now.
<davexunit>if you use GuixSD more, you should fairly quickly find software missing that you'd like to have.
<sir123>Ok. I'll find something to practice on. Looks like GSD will be my daily driver, so I'll find something, surely.
<davexunit>hopefully you'll find something easy to start with :)
<ewemoa>here is an attempt for stacked git:
<mark_weaver>ewemoa: debian seems to think it's gpl2, not gpl3, but otherwise looks good
<mark_weaver>also you should add a copyright line at the top of the file for yourself
<mark_weaver>and post the result of 'git format-patch' to guix-devel when you think it's ready :)
<ewemoa>mark_weaver: re: license -- how confusing... has a link to gpl3 iiuc, yet: mentions gpl2+ ...
<ewemoa>thanks for the feedback
<ewemoa>there is a COPYING file in the tar ball and it seems to say gpl2
<taylanub>in what file would libcap-ng best go?
<iyzsong>mark_weaver: thanks for handing the orc tests! I just back to my keyboard now ;-
<a_e>Hello! I am trying to package python-apsw. Its check phase fails with "ImportError: No module named 'apsw'".
<a_e>Does anyone have any experience with how to handle this?
<civodul>Hello Guix!
<davexunit>hey civo
<civodul>hey! ho!
<davexunit>let's go!
<taylanub>anyone know why I'd get ';;; ERROR: In procedure dynamic-link: file: "/gnu/store/...-gnutls-3.3.12/lib/guile/2.0/guile-gnutls-v-2", message: "file not found"' when guix tries to download via HTTPS?
<davexunit>taylanub: is there actually a .so file there?
<civodul>davexunit: is it 'guix download' or some other command?
<civodul>taylanub: ↑
<civodul>wrong person, sorry
<davexunit>oh okay
<davexunit>I have successfully integrated FRP with the JS rendering library I've been using for guix-web.
<davexunit>now, to actually apply it to guix-web.
<civodul>you mean you have an FRP library in JS?
<davexunit>civodul: yeah
<davexunit>I looked around and picked one that seemed to work the best for me.
<davexunit>none of them work like the one I wrote in Scheme.
<davexunit>this one has been the easiest to work with, IMO
<davexunit>civodul: oh also, I restructed guix-web such that it is now a subcommand of guix. if it ever gets integrated in guix core, it will make the transition smoother.
<taylanub>civodul: it's guix download
<civodul>davexunit: nice!
<civodul>i owe you a couple of patches, BTW
<davexunit>civodul: :)
<civodul>taylanub: then the problem may be that is linked against a different libguile compared to the 'guile' command in the 'guix' shebang
<davexunit>I've started the FRP conversion. things are looking nicer already.
<paroneayea>hi guix
<paroneayea>if I want to try the gsd with qemu, how do I specify to boot... sorry, I'm a qemu newbie here
<paroneayea>I would think:
<paroneayea>xz -d gsd-usb-install-0.8.1.x86_64-linux.xz
<paroneayea>qemu-img create -f qcow2 guixtest.qcow2 900M
<paroneayea>qemu-system-x86_64 -machine accel=kvm,kernel_irqchip=on -hda guixtest.qcow2 -cdrom gsd-usb-install-0.8.1.x86_64-linux
<paroneayea>the -cdrom parameter is clearly wrong though
<a_e>paroneayea: Normally something like this:
<a_e>guix system vm gnu/system/os-config.tmpl
<a_e>The output (last printed line) should be a script that you can simply launch.
<paroneayea>a_e: oh, "guix system vm" does it for you?
<a_e>It sets the correct environment variables and uses the qemu from guix.
<paroneayea>a_e: but that requires that I install guix to my system
<paroneayea>and I'm trying to avoid doing that at the moment and test it in a VM first :)
<a_e>Ah yes, indeed. But it is painless ;-)
<paroneayea>but it's good to know that works
<a_e>Everything is completely separated from the rest of your system.
<paroneayea>a_e: I just have this aversion to installing things outside the system packager
<paroneayea>maybe I should get over it and take the leap
<a_e>Concerning the installation image, I do not know.
<paroneayea>I could just install guix to my debian machine I guess
<davexunit>paroneayea: I run guix from my git checkout, it's not installed to the system, sans the /gnu/store directory.
<paroneayea>I'm just so hesitant :)
<a_e>I installed it into /usr/local/guix, with the packages in /gnu/store.
<a_e>The first step is not necessary.
<paroneayea>davexunit: so everything runs as your user? do you have /gnu/store chown'ed to davexunit? :)
<davexunit>no, the daemon still runs as root
<davexunit>but I never run 'make install'
<paroneayea>davexunit: oh okay
<davexunit>I use the 'pre-inst-env' script to run things
<davexunit>./pre-inst-env guix install mediagoblin # someday...
<paroneayea>davexunit: I'm very interested in that command working :)
<paroneayea>talking to guix folks at fosdem and having mentioned but not having used guix in my talk is making me itch to actually have experience with it ;)
<paroneayea>davexunit: now that I know how to pre-install-env it up with sly though
<paroneayea>I guess I can do it pretty easily with guix :)
<paroneayea>I think this FOSDEM also made me realize that I really want to go to the GNU Hackers Meeting this year
<paroneayea>since I haven't gone before
<paroneayea>and I want closer conversations between mediagoblin and other gnu hackers
<a_e>This would be nice! The more, the merrier!
<davexunit>having mediagoblin easily usable via guix would be a big GNU win, IMO.
<paroneayea>it would be nice :)
<paroneayea>a_e: are you one of the guix hackers I met at fosdem?
*paroneayea is chris webber, if unclear
<a_e>Yes indeed. The one who asked about guix in your talk ;-)
<paroneayea>I thought so :)
<a_e>I see this in your profile.
<paroneayea>a_e: great to make the connection! :)
<a_e>Yes, I have a very cryptic login name...
<paroneayea>a_e: clearly I can judge :)
<a_e>I will leave now. Talk to you another time, and enjoy your guix installation!
<paroneayea>thanks a_e, later! :)
<civodul>hey, paroneayea!
<paroneayea>hi civodul ! :)
<rigelk>hi #guix
<jxself>Ahoy there.
<rigelk>not sure about that, but does the GSD have drivers for SCSI/SAS HDDs ? it might be a problem on old servers
<paroneayea>I wonder if I can get a guilemacs package for guix working.
<jxself>IIRC, the kernel named Linux has supported serial attached SCSI devices for at least ten years.
<DusXMT>rigelk: the drivers are probably there, but they're most probably not included in the default initrd; you have to find how the module is called and add it into your system definition's initrd field, check the documentation for details (the initrd section)
<DusXMT>Tip: The easiest way to find how a module for a device is called is lspci -k
<rigelk>DusXMT, lspci -k will show the currently used driver on the machine i intend to run GSD. That name should be put in the #:extra-modules option list, right ?
<DusXMT>rigelk: Yes, with a .ko at the end
<rigelk>why the .ko ?
<DusXMT>That's a design choice, you'll have to ask someone like civodul
<civodul>*without* .ko
<civodul>it's an implementation detail more than a "design choice" TBH ;-)
<DusXMT>Then the web manual is outdated:
<civodul>but both work
<rigelk>okay. i might just begin to write my server’s system definition
*civodul updates the manual;
<civodul>rigelk: cool!
<civodul>i think you can just take the default template and add (lsh-service)
<civodul>and add a user account called "hydra" (which is the convention we use)
<rigelk>i’m doing that ; will show you for linting ;)
<civodul>ok :-)
<rigelk>here is my system definition :
*paroneayea surprised to see linux-libre being pulled down when not installing guix system
*paroneayea just did guix pacakge -i emacs
<paroneayea>on a debian machine
<DusXMT>paroneayea: It needs the kernel headers to build the libc
<paroneayea>DusXMT: oic
<paroneayea>I suppose that makes sense!
<rekado>the online documentation says that the USB image is located at --- but it is not.
<jgrant>rekado: Change the ftp to http?
<rekado>my point is that the published manual is wrong.
<jgrant>How did you try accessing it?
<rekado>I can find the correct file on ftp, but its name is different.
<jgrant>rekado: Well, ;^)
<rekado>the correct file is one of or
<rekado>no ... I'm actually just too stupid to read.
<rekado>the link is directly followed by "where system is one of: "
<rekado>I do think, though, that there should not be a link that leads nowhere.
<rekado>civodul: what is an account called "hydra" needed for?
<rigelk>rekado, i suppose your mentionning the system definition for an hydra slave, right ?
<mark_weaver>rekado: hydra is the user that logs into the build slaves as, and runs the builds as.
<rekado>I see. I was missing the bit about this being a system definition for a hydra slave.
<taylanub>does guile-gnutls from Guix only work with Guix's own guile builds?
<mark_weaver>you can't mix guix libraries with non guix libraries within the same executable, in general.
*mark_weaver goes afk
*paroneayea authorizes hydra... whew, much faster! ;)
<espectalll123>Hello - anybody could help me? If you don't find me annoying or dull, of course :)
<espectalll123>...guess that's a no xD
<DusXMT>espectalll123: just ask your question, if someone knows, they'll reply
<espectalll123>Where are the executables? I can't execute it from Bash (it's not at one of the path folders) and there's nothing useful at /gnu/store
<paroneayea>so what's up with the guix project and hardware, ie hardware useful to add to hydra?
<paroneayea>thinking about whether I could toss in a few bucks to help guix and hydra stuff on arm
<espectalll123>DusXMT: The file does not exist :/
<DusXMT>espectalll123: Have you installed anything as the given user?
<paroneayea>the cubieboard 4 is supposedly libre hardware (can't find such files though) and provides 2GB ram
<paroneayea>which is probably more than enough to help guix bootstrap stuff in hydra right?
<paroneayea>and only ~$50
<DusXMT>Or were you "clever" and put `sudo' in front of every guix command? ;)
<rigelk>paroneayea, i’m building a cluster of machines to help hydra build - all the machines are old servers gathered here and there
<espectalll123>DusXMT: Only did 'guix pull'. So... yes?
<DusXMT>espectalll123: in that case, there's nothing in your profile, so there's no profile. Just do `guix package -i pkgname' to install stuff, it'll end up in ~/.guix-profile
<paroneayea>hi rigelk
<DusXMT>For example, `guix package -i hello' to install Hello World, the GNU version
<jgrant>Okay, seeding the fudge out of the GSD torrents.
<espectalll123>DusXMT: If I do that, it tries to compile everything from the Linux-libre kernel. And with --dry-run it seems to be succesfull but does nothing at all.
<DusXMT>espectalll123: the "linux-libre kernel" are just header files...
<espectalll123>DusXMT: Still, have to compile everything. And, again!?
<DusXMT>espectalll123: You can enable substitutes if you trust our buld farm, and use binaries :)
<espectalll123>DusXMT: Enable, it seems to be unable to connect to the GNU repo
<DusXMT>Just wait, it can take some time, but once a connection to Hydra is established, it shouldn't be that bad
<espectalll123>substitute-binary: guix substitute-binary: warning: ACL for archive imports seems to be uninitialized, substitutes may be unavailable
<DusXMT>espectalll123: in that case, you haven't authorized hydra, check the docs
<DusXMT>ie. you didn;t enable them
<rigelk>paroneayea, i think your bucks might be used in a better way than by buying a cubieboard
<espectalll123>I'm derp. I guess I didn't load the keys from the correct path
<rigelk>paroneayea, if i remember, some people are trying to gather enough money to buy another (recent) server. don’t know if it’s still up-to-date
<paroneayea>rigelk: ok :)
<paroneayea>(I'm not sure why hydra can't use qemu to build the arm packages anwyay?)
<paroneayea>maybe something obvious I don't know
<paroneayea>ERROR: In procedure module-lookup: Unbound variable: %guix-dir
<paroneayea>when running M-x guix-all-available-packages
<espectalll123>DusXMT: 'guix package -i hello --dry-run' does exactly the same: nothing. Except no warnings.
<paroneayea>I have
<paroneayea>(add-to-list 'load-path "/home/cwebber/devel/guix/emacs")
<paroneayea>(require 'guix-init)
<DusXMT>espectalll123: And that's exactly what --dry-run means, do nothing...
<espectalll123>DusXMT: Wasn't it just avoiding to compile/install *other* dependant packages?
<espectalll123>I'm really that idiot? -.-
<DusXMT>Nope, it was to demonstrate in the docs that it wouldn't build, but download the packages...
<espectalll123>OK, thank you.
<DusXMT>Comparing the outputs before and after
<espectalll123>I seriously have to master this package manager. Not as dumb as an apt-get, as I should have guessed.
<DusXMT>espectalll123: note: apt is more than just apt-get :)
<espectalll123>I know. dpkg is as simple :P
<espectalll123>espectalll123@iMac:~$ ~/.guix-profile/bin/hello
<espectalll123>Hello, world!
<espectalll123>DusXMT: Thank you!!! Finally working ^_^
<rigelk>sorry, wrong buffer ^^'
<paroneayea>so I guess it's obvious that ~/.guix-profile/bin/ needs to be added to ones' PATH then ;)
<taylanub>paroneayea: yes :)
<taylanub>paroneayea: guix package --search-paths to output an sh snippet for exporting useful environment variables
<paroneayea>taylanub: doesn't output anything..:)
<paroneayea>cwebber@earlgrey:~/devel/guix$ guix package --search-paths
<davexunit>that means you haven't installed anything that needs a search path set
*paroneayea wonders why he can't get the emacs integration working right
<paroneayea>it's probably because I didn't "make install", huh
<paroneayea>davexunit: ping
<paroneayea>did you have any extra steps for doing the emacs integration, without doing make install?
<paroneayea>like, maybe something needs to be added to the guile path, or something...
<paroneayea>in order for the geiser support to work?
<davexunit>I think you need to set GUILE_LOAD_PATH and GUILE_LOAD_COMPILED_PATH
<paroneayea>davexunit: any relevant snippets you can share?
<davexunit>maybe... let me look
<paroneayea>assuming you did this yourself
<davexunit>honestly I haven't set this up too well.
<paroneayea>thanks davexunit :)
<paroneayea>ah, okay
<paroneayea>sorry, I don't mean to be a bother
<davexunit>export GUILE_LOAD_PATH=/path/to/guix:$GUILE_LOAD_PATH
<davexunit>same for GUILE_LOAD_COMPILED_PATH
<davexunit>oh sweet, I actually have this in my Emacs init.el:
<davexunit>(add-to-list 'load-path "~/Code/guix/emacs")
<davexunit>(setenv "GUILE_LOAD_PATH" "/home/dave/Code/guix")
<davexunit>(setenv "GUILE_LOAD_COMPILED_PATH" "/home/dave/Code/guix")
<paroneayea>okay I'll set that.
<paroneayea>davexunit: heh, I found logs of you discussing this same issue ;)
<davexunit>full circle :P
<paroneayea>it doesn't look like you solved it
<davexunit>IIRC, that problem was resolved eventually
<davexunit>on my debian system, the snippet I showed you is enough to use guix.el
<paroneayea>davexunit: hm
<paroneayea>I wonder why I can't get it to work then :(
<davexunit>what error do you get now?
<paroneayea>ERROR: In procedure module-lookup: Unbound variable: %guix-dir
<paroneayea>same as before it seems
<paroneayea>no, yeah, same thing
<paroneayea>Maybe I should install geiser through guix, I dunno
<davexunit> open a geiser REPL and type ",m (guix config)"
<davexunit>it worked?
<paroneayea>oh, should that fix guix integration? :)
<paroneayea>I'll try again
<paroneayea>yes it worked though
<davexunit>it won't fix it
<davexunit>just a test
<davexunit>to see if the load path was somewhat correct
<davexunit>paroneayea: try evaluating '(require 'guix-autoloads)' in emacs
<paroneayea>davexunit: works fine
<paroneayea>(require 'geiser-install), mentioned in the above linked irc logs, does not tho
<davexunit>well, you have geiser loaded, so don't worry about that
<davexunit>does 'M-x guix-all-available-packages' work now?
<paroneayea>no, but it switched the error to:
<paroneayea>socket:44:16: In procedure module-lookup: Unbound variable: entries
<paroneayea>I wish I knew where the failure was coming from.
<davexunit>the backtrace should be somewhere
<paroneayea>the backtrace is pretty unhelpful:
<paroneayea>scheme@(guix config) [1]> ,backtrace
<paroneayea> 1 (eval (#<procedure 2a58e00>) #<directory (guix config) 29b7ea0>)
<paroneayea>In socket:
<paroneayea> 54:16 0 (#<procedure 2a58c60 at socket:54:16 ()>)
<paroneayea>that's it
<alezost>paroneayea: is it GuixSD or guix on top of some distro?
<paroneayea>alezost: guix on top of debian
<paroneayea>but I didn't do a make install
<paroneayea>using pre-inst-env
<davexunit>paroneayea: alezost wrote guix.el and will surely be more helpful than I
<paroneayea>hi alezost :)
<alezost>paroneayea: hi, so you didn't install guix in your system?
<paroneayea>alezost: no make install, correct
<paroneayea>though I'm still running it
<paroneayea>and guix works
<alezost>paroneayea: so after (require 'guix-init) and some "M-x guix-…" command you are getting "Unbound variable: %guix-dir". Right?
<paroneayea>alezost: yes
<alezost>paroneayea: could you check the value of `guix-load-path' var
<alezost>(emacs variable)
<alezost>and the value of %load-path in *Guix REPL*
<paroneayea>$6 = ("/home/cwebber/.emacs.d/el-get/geiser/scheme/guile/" "/usr/local/share/guile/site/2.0/guix/emacs" "/home/cwebber/devel/guix" "/usr/share/guile/2.0" "/usr/share/guile/site/2.0" "/usr/share/guile/site" "/usr/share/guile")
<alezost>paroneayea: is the value of `guix-helper-file' var "/usr/local/share/guile/site/2.0/guix/emacs/guix-helper.scm"?
<paroneayea>"/usr/local/share/guile/site/2.0/guix/emacs/guix-helper.scm" ... seems like it!
<alezost>IIUC there is no such dir ("/usr/local/share/guile/site/2.0/guix/emacs") ?
<paroneayea>and aha, of course
<paroneayea>let me try changing that
<alezost>paroneayea: try to add (setq guix-load-path "/home/cwebber/devel/guix/emacs") to your emacs config along with (add-to-list …) and (require …)
<paroneayea>alezost: trying!
<paroneayea>alezost: fixed!
<paroneayea>alezost: I will put up a blogpost explaining how I got that to work then. :)
<paroneayea>thank you for all your help, alezost !
<alezost>Great, no problem! Yeah, there are several ways of using guix and thus its emacs interface: on GuixSD 0.8.1 it should work out of the box. For guix installed on top of another distro you need those 2 lines mentioned in the manual. Apparently for this case (without installing) one also needs to change `guix-load-path' var. Thanks for the patience!
<rekado>Just installed GNU GSD on a Thinkpad T60.
<fchmmr>rekado, does that T60 have libreboot on it?
<rekado>not yet.
<rekado>it's one of my father's old machines, and I just got it.
<rekado>fchmmr: is libreboot known to work with the T60?
<fchmmr>rekado, if it has an intel gma 950 graphics, and a compatible screen, yes.
<fchmmr>I'm running libreboot on a T60 and using it to talk to you at this moment.
<rekado>First thing I did after rebooting was set a password and then start a WindowMaker session.
<rekado>When I wanted to change the style, though, I got an error saying that setstyle failed.
<rekado>I get similar errors for other WindowMaker commands.
<rekado>I note that setstyle is in /gnu/store/...-windowmaker-.../bin
<rekado>but it's not in my PATH.
<rekado>(I used the configuration template with almost no changes at all.)
<rekado>Is this behaviour expected?
<rekado>The exact error is "Could not execute command: setstyle /gnu/store/...windowmaker.../share/WindowMaker/Styles/
<rekado>Another error when I click on "Configure Window Maker" in the menu: "Could not execute command: exec WPrefs"
<Gabou>fchmmr: waiting GSD to support lvm to try it :P