<zacchae[m]>apteryx: I suspect the problem is due to my home env being grossly out of date (still waiting on that qutebrowser patch).
<zacchae[m]>Even in my out-of-date system, I think the problem has something to do with my profile and home env not playing nicely, so I tried getting a similar scenario with guix home container to see, but adding python to the home environment specification did not give me access in the container, so I'm not sure how I'd go about reproducing
<bjc>EMax`0Mancer[m]: so i got around to installing gnome and gdm, and it looks like its not going to work; /run/current-system/share/xsessions is a symlink *into* the gnome session share
<bjc>i had assumed that it would contain symlinks into various packages to collect desktop entries, like other parts of the system do (/run/current-system/share/applications, for example)
<bjc>this seems like a bug/oversight to me, since i dunno how it'd be extended for other desktop environments this way
***rekado_ is now known as rekado
<Gooberpatrol66>Anyone know how to use lv2 plugins on guix? The directories listed in $LV2_PATH don't exist.
<EMax`0Mancer[m]><bjc> "this seems like a bug/oversight..." <- I can't seem to find any other place where gdm will look. I tried creating a /usr/local/share directory, but that didn't work.
<bjc>from what i can see in gnu/services/xorg.scm, it looks as though gdm will also look in your local profile
<bjc>so ~/.guix-profile/share/xsessions/whatever.desktop might show up in the picker
<bjc>i'm not sure how that works inside gdm -- you may have to enter at least your login before it shows up; i've never used per-user session definitions inside a greeter before
<bjc>that said, there should be a way for other desktop environments, installed via guix system, to insert their desktop entries globally. if there isn't i would personally call that a bug, but i may be missing something in how guix is meant to operate. you may do well asking on the mailing list
<jpoiret>by default, if a derivation is already built, it won't be rebuilt
<jpoiret>you can use --check to force an independent rebuid
***bjc`` is now known as bjc
<eskin>Hi all, new to guix/guile.. I've tried to install guile libraries "haunt" and "artanis" through guix home, but that doesn't seem to add them to my guile load path
<eskin>Does anyone know a way to make it so guile libraries are added to the load path automatically when they're installed that way?
<eskin>The binaries are accessible, but if I try to use any of the libraries` modules at the repl it doesnt recognize them
<bjc`>eskin: often times when things are meant to go into a shared path, you'll find them underneath your profile/home share path
***bjc` is now known as bjc
<bjc>in this case, artanis stuff can be found in ~/.guix-home/profile/share/guile/site/3.0
<bjc>(as would other libraries installed via guix home)
<bjc>if you'd installed it with ‘guix package’ instead, it'd be under ~/.guix-profile (or the path to the profile you installed it under, if you specified that explicitly)
<jpoiret>eskin: you need to also have `guile` installed in the profile for the search paths to be considered
<jpoiret>think of those like plugins: you need the base software to be installed for the plugins to be picked up
<PotentialUser-84>Hi I have something I'm sort of confused about. I'm using TMB which is an R package where you build models using C++ templates. So minimum you need the following packages to make it work "r","r-tmb","gcc-toolchain","make","gfortran-toolchain"
<jpoiret>i don't think you'll find much, it's a very internal error
<jpoiret>i don't want to discourage you but maybe your time is better spent on something else :p
<jpoiret>your photos are already very helpful in tracking down the source of the bug
<SrEstegosaurio[m>Okey I understand. The problem is that at first I tried using the "stable" release. It kinda worked untill the GRUB part. So someone recommend me to use the newest one instead but it seams to not be working tho.
<jpoiret>Guix is not really responsible for the final grub binary that's installed either in the EFI partition as .efi or embedded in the first sectors of the mbr, it's grub-install that pieces the needed bits together
<jpoiret>basically, grub-install takes the standard grub binary and adds a bunch of things to it, like default modules used for accessing /boot/grub and some other things
<jpoiret>that's at the root of another problem: GRUB supports luks2 but grub-install doesn't properly detect luks2 devices, so it won't embed the luks2 module if /boot/grub is on a luks2-encrypted drive
<bjc>grub-install builds the binary, or grub-mkimage? i've only used the latter to build a custom grub with statically linked modules
<bjc>yeah, i've only had to mess with this for building grub images for foreign systems, so anything in grub-install wouldn't work for me
<bjc>the bootloader has to use the "grub" package for its paths, right? so theoretically, you could create a new package called "grub", inheriting the old one, then have a build step that does a "grub-mkimage" that includes lvm, and that package would be picked up by the bootloader module?
<bjc>obviously the ability to declare extra modules is preferable to that, but in the mean-time, would that work as a hack around the problem?
<jpoiret>bjc: rather, you'd have to modify the definition of grub-efi-bootloader to be able to include additional pre-built modules
<bjc>with string-append, how would that work? how do i get the "lib" output path for the first argument?
<apteryx>bjc: by the way, if you are interested in ZFS, there are patches on the guix-patches tracker sitting for months; perhaps you are the person those patches have been waiting for (to get proper testing/feedback)
<bjc>i've seen them, and it looked like they were integrated already
<ZhuAisi[m]>My thoughts: There may be some user config if somebody use declarative configuration
<bjc>the distinction between /usr and / is arbitrary and dates to a time when disks were very, very small
<bjc>i'd argue it hasn't been a relevant distinction for decades, but it's stuck with us due to long-encoded path expectations
<jpoiret>the FHS fails to be clear on what /usr is for exactly
<bjc>and /gnu/store is an entirely different beast that doesn't map to the unix heirarchy in any meaningful way
<ZhuAisi[m]>bjc: The main issue is, I found some software ro mount /usr to sandbox(e.g. flatpak). Some Nix guys patch this behaviour to mount nix store instead. But I don't think store is equivalent to /usr in security aspect
<bjc>what i mean is, since the result of lower-object on (pkg "out") is the same as (pkg "lib"), which is a derivation of pkg, and the derivation is what needs to be queried for the paths based on output, i don't think it makes much sense for lower-object to care about the output
<bjc>actually, yeah, i've just talked myself out of putting it there
<bjc>grub will then load all its things off the efi partition, including its config, and then do whatever the config specifies
<WesterWest[m]>but before it opens grub menu it asks me for the password to the second partition (and is qwerty) after that grub menu appears and when I select guix option it asks me for my password again
<bjc>i don't know why you'd have to unlock twice during boot, and particularly not with different keymaps. grub should know enough by the time it prompts you to for a password to have your keymap set up
<bjc>huh. wild. dunno why it does that. i'm not particularly familiar with luks, though, so maybe that's normal?
<acrow>I have been using guix-home and I've noticed that if I run, for instance, 'guix package -u flatpak' I get the 'consider setting the necessary environment variable ... GUIX_PROFILE... ' hint.
<acrow>I usually love the hints but in this case it offers that I should set GUIX_PROFILE to "$HOME/.guix-profile" but since I am a user of guix-home, GUIX_PROFILE="$HOME/.guix-home/profile". I think this is wrong. Or, maybe, as a home user, I am not expected to run 'guix package -u'? I think the hint might be improved. Hmmmm.
<zacchae[m]>Because guix home will do it right, but if you try and run those sort of commands yourself, you might mess things up. Specifically, running the guix profile command will erase guix-home from your path, which is not what you want
<zacchae[m]>On an unrelated note, does anyone self-host an email server on Guix? I want to know if I just need to set up dovecot, or if I need more services (like exim or opensmtp)
<singpolyma>zacchae[m]: dovecot isn't a mailserver so you almost certainly need a second thing
<bjc>and more on top of that for modern mail. at least a dkim implementation
<bjc>not on guix, though, so i can't help you with specifics there
<zacchae[m]>Thanks singpolyma, bjc. For now it's just me, so I think something like a maildir setup should be fine if I understand correctly. So what I'm looking for is a MTA then? So exim is the bare minimum?
<acrow>zacchae: That makes sense. So. If you are using guix home you need to either ignore the hints or avoid running guix package command, no? Instead depend entirely on home-configuration.scm and then home reconfigure. IIUC.
<bjc>personally, i'd recommend postfix over exim, since it's much easier to configure and manage for a self-hosted setup
<bjc>postfix+dovecot+opendkim will be what you need for basic reception and delivery, i believe. unfortunately i set my stuff up a long time ago and have been migrating it by way of zfs send/recv, so i have long lost the specifics of everything that's needed
<zacchae[m]>acrow: You should ignore that warning I believe, as that is already run if you configure your shell with guix-home. See ~/.profile -> sources /etc/profile -> runs the lines indicated in that warning
<Haider>Small question, I am trying to package a package where I had to package it's dependancy also as Guix's version is out-of date, How do I tell the package to use the local .scm packaged version instead of the committed version
<zacchae[m]>bjc: I don't see postfix in the guix user manual, so I'll probably stick with exim
<bjc>ah, fair enough. i didn't know guix lacked postfix
<zacchae[m]>Haider: I believe you can add the directory with your local .scm (see guix -L) and import it normally