<ZombieChicken>civodul: Ran into an issue using LUKS atop RAID. Grub was apparently trying to use lvm/root for the root filesystem, which made no sense to me <lfam>civodul: Is it okay if I delete the staging Git branch? <lfam>Or I suppose we could just merge master back into it and keep it open for the next cycle, WDYT? <civodul>i'd delete it and recreate it when needed <civodul>ZombieChicken: if 'grub-install' wrote an error message about 'lvm/root' being not found, then you're using a GRUB that is too old (not with the fix i mentioned earlier here) <ZombieChicken>About how long ago was that and I'll just look through my logs <civodul>this is what allows 'grub-install' to properly detect cryptsetup root partitions <civodul>so if you use a recent-enough GuixSD, you shouldn't have the 'lvm/root' error from GRUB <ZombieChicken>I always do a guix pull before installing, so unless I'm mistaken that should resolve that <civodul>provided you run 'guix pull' as root <civodul>sorry, i had overlooked this tiny detail ;-) <arescorpio> an open-source implementation of the OpenGL specification <paroneayea>lfam: <jrollins> cwebber: 0.10 is in debian testing <paroneayea>so, sounds like we can move forward with it as a release. ***jje is now known as Guest59961
***Guest59961 is now known as jje
<kyamashita>Do we have a way to deal with the dates in compiled .pyc files besides removing them (the .pyc files)? <roptat>hi, I have an issue building swig from master <roptat>configure failes with "./configure: line 27: /dev/null: Permission denied" <kyamashita>roptat: Building swig from source right now (no substitutes). <roptat>how can I make sure I run the latest guix-daemon? <kyamashita>roptat: Also, you will need to reconfigure your system if you are using GuixSD. <roptat>guix pull tries to build swig... <kyamashita>roptat: How are you running Guix? On GuixSD or on a "foriegn" distro? <kyamashita>Do you know what version of guix-daemon and guix are you running? <kyamashita>P.S. You can use the "guix-daemon --version" and "guix --version" to find their exact values. <kyamashita>I wonder why "guix pull" is trying to build swig. It clearly is not listed as a dependency. <kyamashita>roptat: Could you paste your "guix pull --verbose" output to paste.lisp.org and post the link here? <roptat>ok, actually I think it's my fault <roptat>I wrote a udev rule that override the permission on /dev/null <roptat>it wasn't intended, but I feel stupid not to have checked that before... <sneek>Welcome back ovidnis`, you have 1 message. <sneek>ovidnis`, alezost says: so you installed "sbcl-stumpwm:bin" in your user profile, right? I think that SLIM looks for .desktop files only in a system profile, so you need to install stumpwm globally, i.e. try to add (packages (list sbcl-stumpwm "bin") ...) to your system config <joshuaBPMan_>Hello, I'm currently unable to log into gnome as my normal root user. I'm dual booting. I'm trying to figure out where to read log massages. GuixSD uses syslog right? <kyamashita>joshuaBPMan_: I don't know about syslog, but I know logs typically get dumped onto /dev/tty1 on GuixSD. I haven't figured out how to access them yet. <joshuaBPMan_>kyamashita: What is really sad, is that I only a few days ago I did know how to access the logs. <joshuaBPMan_>I have errors from gnome-session-binary and gnome-keyring-daemon stored in a file on my computer. <joshuaBPMan_>BUT I just reconfigured. And I want to make sure that the reason that I can't log in, is still the same. <joshuaBPMan_>Also, I was using a hack to dual boot properly that relied on a bug. They since fixed that bug. Which was why I needed to reconfigure. <kyamashita>The rottlog-service document talks about that. My /dev/tty1 seems to mirror most of my /var/log/messages file. <joshuaBPMan_>I've got a gnome-keyring-daemon error from today at 4pm. That was probably when I tried to log into gnome as a normal user.