<drewc>Hello All! I just recently started trying GuixSD on my thinkpad. Everything seems to work great save for the wifi. I am assuming it is a nonfree firmware, and googling finds me a number of .scm's, so where should I start?
<buenouanq>I don't know if the official people as part of gnu can help with nonfree terribleness - It's something they explicitly do not support. I would start with whatever Debian says about your chip. I would suggest getting something like the freedom respecting Think Penguin dongle.
<buenouanq>That is an interesting question - Are you guys bound to not help with nonfree drivers and stuff?
<drewc>Fair enough. Please allow me to follow with a question that does not invalidate anyones freedom. I have a linux-social.scm which I found on google, which contains a number of packages that are not in the mainline, as they are kernel patches that are not for the light of heart, to make it run on hardware that only I possess. What is the simple way to use that .scm to test it out?
<mange>I think you should be able to replace the "kernel" field in your operating-system declaration with a package that specifies a different kernel.
<drewc>Makes sense, I've seen something similar in my search results. In order to do that where/how should I place/import the "linux-social.scm" file that I found so that `guix system reconfigure` will have the packages available?
<cbaines>drewc, it just needs to be on the GUILE_LOAD_PATH, in the correct directory structure
<cbaines>at the top, there will probably be a line begining (define-module (... e.g. (define-module (gnu packages linux)
<cbaines>I believe you will need to place the file in a directory structure matching each module namespace, e.g. gnu/packages/linux.scm for the above example
<mange>It's hard to say exactly what you have to do, because it depends a bit on the contents of linux-social.scm, but cbaines is right about the load path. You can also add directories to the load path with the --load-path= argument to `guix system`.
<drewc>awesome, that should point me in the right direction. Thanks a bunch!
<nextos>lfam: thanks. makes sense, texlive is huge and most files are not being built
<lfam>nextos: There's been discussion on guix-devel of breaking the big texlive-texmf package into modules, but it's complicated
<sneek>baconicsynergy, rekado says: When building things with Guix it doesn’t matter what you have installed locally. All that matters is what the package expression declares as inputs, as these are the only things that appear in the build environment.
<jmd>Starting the cow-store service seems to corrupt /tmp
<davexunit>lfam, buenouanq: nginx has default log and run directories set at build time, and upon install time it creates those directories, therefore without some hackery you cannot set the defaults to /var/log/nginx and /var/run/nginx because there is no /var in the build container.
<davexunit>this is why you currently have to configure them manually.
<davexunit>maybe someone really wanted to use opengl 4.4 :)
<jmd>Is there a way to find out which Guix os is currently running?
<drtan>Hi! I am playing with Guix SD inside a VM (QEMU KVM). I've tried the installation on an encrypted partition (LUKS) and everything worked well until reboot. GRUB can't see the partition. When I boot back the install image and try to open the partition it is not recognised by cryptsetup. Is there anything I could have forgotten?
<davexunit>guix produces derivations which are built by guix-daemon and they produce store items. in the case of GuixSD one of those store items is a new GRUB configuration that gets installed upon 'guix system init' and 'guix system reconfigure'
<davexunit>you can't look at anything produced and know which version of guix produced it. does that make sense?
<lfam>My understanding is that we added the minimally viable nginx service, and now we can improve it as necessary :)
<drewc>What are the proper ways to use GuixSD yet run a bunch of shebang scripts (like #!/usr/bin/env bash )? Is there a simple trick I am missing when `whereis env` says what it says?
<lfam>drewc: What do you mean by "Is there a simple trick I am missing when `whereis env` says what it says?"
<lfam>In general, if you don't care that your scripts won't get the benefits of Guix, and might break randomly like on a "traditional" distro, you could just symlink the env binary to /usr/bin/env
<lfam>The question of shell scripts on Guix has been discussed many times, and I'm not sure if anyone came up with a good solution in the last few discussions. You might check the guix-devel and help-guix archives
<buenouanq>`Warning: untrusted X11 forwarding setup failed: xauth key data not generated'
<buenouanq>I can't get ssh -X to work from a GuixSD machine, though it will work from a Debian to a GuixSD machine.
<lfam>buenouanq: Did you check to see if there's already a bug report?
<drewc>lfam: Yeah, that is what I am doing, but I was hoping there was something simpler. I am trying to build chromium, and hoping to do a chromium.scm you see. The docs require a bunch of dependencies which may or may not require /usr/bin etc, which is probably not what is wanted or even allowed for a GuixSD package. Thanks for the confirmation :)
<lfam>drewc: The Guix build systems automatically patch shebangs. So if you are making a package, it shouldn't be an issue
<lfam>If you want to try building it outside of a Guix package (by hand), you could try using the patch-source-shebangs Guile procedure on the source tree manually
***propumpkin is now known as copumpkin
<drewc>oh, does it automagically do so? That sounds so wonderful! I'll look at the docs at try the manual procedure thing as well. W00t!