<reepca>rain1: as far as I can tell it would require either adding more information to every package definition (would require quite a bit of changing) or knowing what every package looks like in its built form.
<reepca>quiliro: the daemon shouldn't be necessary for client stuff to work
<ng0>sneek: later tell quiliro: you have to include 'openssh' in the system wide available packages. This makes the 'scp' binary available to connecting users
<janneke>rain1: really want to see how we can make good use of that
<janneke>also i didn't try out/follow up on your 8cc patch yet
<rain1>ah the thing was after removing the anon. union there is a few uses of va_list
<reepca>There's a lot of code in guix/store.scm that does basically what I want, but relies on RPCs for low-level functionality - mostly accessing the database. It feels weird duplicating code just to replace the implementation of some low-level thing. I wonder if there's a better way.
<janneke>oh yeah, that's right -- that needs more inspection and thought
<mekeor>any idea why "guix environment guix" results in "error: profile contains conflicting entries for gzip:out" for me?
<mekeor>i wonder if it was a mistake that i once did "./pre-inst-env guix package -i …"
<mekeor>yes, i could run "./pre-inst-env guix package -r ..." but i already did "git pull", so the pre-installation-environment changed.
<mekeor>i had ghc-xmonad-contrib package installed both as system-package as well as user. i now removed all system-generations; also removed xmonad as user; removed all old user-generations; and finally ran "guix gc" both as root and as user. but there are still files and folders for ghc-xmonad-contrib in /gnu/store. why?
<mekeor>s/xmonad as user/ghc-xmonad-contrib as user/
<jlicht>for me, as root: cd .config/guix; ln -s <wherever your git checkout of guix is> ./latest
<jlicht>there should already be a symlink called latest in that directory; if you are not really sure of what you are doing yet, I recommend simply renaming instead of overwriting the symlink, so you can easily revert to a known working guix for root in case something goes terribly wrong ;-)
<jlicht>but maybe some of the more knowledgable folks around here can share their workflows: this is just what works for me :D
<dfh_>So. I just managed to get GuixSD installed on my new old X200s. Now trying to install some fonts. Not going all too well. I'm wondering, how can I tell what fonts are installed?
<AndChat438900>Hi all. I installed guix. all is good. I restarted my pc. The grub worked well. But after the grub there are several messages displayed on the screen and before going to the connection window guix blocked
<espectalll>By "connection window" you mean login screen, right?
<espectalll>And I guess you have installed GuixSD with a desktop service?
<mekeor>what do you mean by "blocked", AndChat438900
<AndChat438900>(use-modules (gnu) (gnu system nss)) (use-service-modules desktop) (use-package-modules certs gnome) (operating-system (host-name "antelope") (timezone "Europe/Paris") (locale "en_US.utf8") ;; Assuming /dev/sdX is the target hard disk, and "my-root" ;; is the label of the target root file system. (bootloader (grub-configuration (device "/dev/sda"))) ;; Specify a mapped device for the encrypted root partition. ;; The UUID is that returned by 'cryptset
<espectalll>Next time, please upload the file with a pastebin, such as paste.lisp.org
<rekado_>ACTION plays a Star Trek game on a PS/2 386 running FreeDOS.
<OriansJ``>janneke: and we now have new and improved tests for MESCC_Tools, now we have examples for both x86 and amd64 working in M0 and a proper changelog so that it'll be a proper project from here on.