<rictjo>good day everyone. I am having a problem with upgrading my guix system. It can build but after the switch to kernel 5.10 from 5.9 it says it cannot find my root luks partition anymore. Displaying an error from ice-9/boot-9. However I can boot the old config. I also tried using an almost identical config file but there is something that I don't understand here. I am completely new to this system and started using it 2020-12-25 (working config a
<mdevos>rictjo: your message seems to be cut of after ‘(working config a’
<leoprikler>If it's the kernel, you should be able to fetch an old one using inferiors.
<vagrantc>rictjo: possibly a change of needed available kernel modules to mount your root device?
<vagrantc>sometimes happens between major kernel versions
<vagrantc>rictjo: you also might try using an older kernel with the same updated config otherwise
<vagrantc>rictjo: i think linux-libre 5.4 should also be available ... and that could rule out a problem with newer software and really identify that it was the kernel that was the problem
<rictjo>There was another quirky behaviour. I am using a swedish keyboard keymap and by intial grub image boots fine and I enter the encryption password. But the boot image keymap was not swedish even though it is set by the intial graphical installer generation script to swedish everywhere
<mdevos>if I understand correctly: when booting, GRUB asks for password with swedish keyboard (weird, GRUB in Guix doesn't yet support setting the keyboard layout before disk decryption), and when booting Linux, Linux asks for a password with a non-swedish keyboard (I presume qwerty?)
<mdevos>rictjo: you can test what GRUB uses, by entering a bogus password, then typing random characters to test in the rescue shell
<rictjo>aha no I was being unclear and I see it is intended behaviour
<rictjo>I was entering the encryption password with US keyboard setting (the hardware is swedish)
<leoprikler>raghavgururajan: looking at it, it seems like they want to generate some xml file from something else, but are failing, because a) it isn't writable (try to make-file-writable before) and and b) some weirdness in etree, that doesn't allow you to pass raw filenames
<leoprikler>if b) would actually be caught somewhere it's actually just a)
*dftxbs3e is working on packaging gutenprint/gimp-print for their canon printer (also supports many others)
<sakalli>hi all. n00b here. if i want to write a package that downloads a gtk package from github and makes it accessible from a specific path. the package has no build files. what would be the simplest way of doing it. is there perhaps an example you could point me to. as an aside, installing gnome-themes-standard/extra does not show up as options for my theme manager. using lxapparence. the pacakges are downloaded to the store tho.
<rictjo>I posted previously about an error with LUKS devices during boot. It seems as though everything is working as intended but the problem arises when I want to place my home on a completely different encrypted drive than the root and boot. I see a reported warning that the new drive _might_ not be moutned during boot. After selecting the new image and entering the pass for the root and boot drive the locking is aborting saying that /run/cryptsetu
<rictjo>that it could not acquire a read lock on the device
<sakalli>sorry see that i was expressing myself confusingly above. just to be clear, talking about writing a package that installs a gtk-theme from github.
<rictjo>I was able to create my system config by first mounting my encrypted device
<rictjo>which was not present when the root,boot and home was placed on the same disk
<jlicht>roptat: If you don't have time to play around /w GUIX_EXTENSIONS_PATH, I can have a look
<rekado_>jlicht: the entry point module needs to be installed to /share/guix/extensions/<command>.scm
<jlicht>rekado_: yeah, I was looking at your recent work on the gwl to see what's what
<jlicht>the only question I still have is how/where/when to 'install' an extension :)
<jlicht>as I only used the latest gwl with `./pre-inst-env' and GUIX_EXTENSIONS_PATH set, from a git repo
<abcdw>leoprikler, civodul: yesterday I digged into systemd implementation a little and it seems that it starts user-space process with pam. pam looks like a more general than .profile for starting user-space shepherd. What do you think?
<abcdw>civodul: 1. lingering-shepherd is not always desired. 2. I also faced following issue with it: When you run a shepherd whithout user session it complains about missing XDG_RUNTIME_DIR/shepherd, which usually created by (probably) pam_elogind on user login.
<apteryx>it is possible the GNU libc regex-exec changed its behavior since 2018 (or perhaps it was Guile 3?) It used to throw an exception when processing a string containing NULs; now it seems to just stop processing upon encountering NUL.
<rekado_>jlicht: you just install it into your profile and manually set GUIX_EXTENSIONS_PATH to $GUIX_PROFILE/share/guix/extensions
<rekado_>it might work to install the extension into the “guix pull” profile, which should cause GUIX_EXTENSIONS_PATH to be set automatically, but I don’t think that’s a good idea.
<rekado_>(because I can’t say how this should be upgraded)
<rekado_>you know, “guix pull” could also upgrade all *other* packages in its profile
<rekado_>or channels.scm could have a field “extensions” with a list of *packages* to install into that profile.
<rekado_>civodul: what do you think about that? Add support for a “packages” or “extensions” field to the “channels” file, which would make “guix pull” install that package into the profile once “guix pull” has completed.
<apteryx>eh, was Guix circa early 2018 still on Guile < 1.8.2? Guile's changelog for 1.8.2 says: ** `regexp-exec' doesn't abort() on #\nul in the input or bad flags arg
<khassanov><lfam "khassanov: I add that to the (se"> Thank you, it works!
<dongcarl>Would --build/host=i686-unknown-linux-gnu have something to do with this?
<civodul>email@example.com is built by firstname.lastname@example.org
<civodul>no that's fine, this option just makes things explicit
<dongcarl>Okay, so here's a conundrum: I am in my older Guix version, and the bash-mesboot0 is in the newer version, so I can't directly do: guix environment -e '(@@ (gnu packages commencement) bash-whatever)'
<dongcarl>And I think if I use time-machine, it will try to build the package that's causing this in the first place, and fail...
*dongcarl really wishes it were possible to do `guix environment` on a derivation
<jonsger>somehow debbugs doesn't like me anymore. I can not close bugs anymore...
<raingloom>how do i convince D-Bus to let me start snapperd? it's not picking up the config from the --ad-hoc env. do i have to install snapper globally or something?
<apteryx>Should the Guix test suite be ran under a given locale, as otherwise it'd be susceptible to user chosen ones?
*jonsger adds `fail2ban` to his personal todo list...
<apteryx>civodul: do you think we can close #26948, or is there something more we could do?
<apteryx>It seems the issue was that "Guile does not allows us to specify whether/how file names should be decoded". Wouldn't setlocale be used for this?
<antidoto>I am trying to schedule a job using mcron. I have added something.guile in ~/.config/cron and then running mcron the cursor just hangs and sudo mcron gives me: Cannot read files in your ~/.config/cron (or ~/.cron) directory. With sudo herd status I can see that mcron is running.
<antidoto>Cannot read files in your ~/.config/cron (or ~/.cron) directory is also the output in mcron --schedule=5
<apteryx>antidoto: so when running as your user the cursor hangs?
<apteryx>jonsger: I just used emacs-debbugs to send done to 45047, thank you!
<apteryx>antidoto: I thought I had a local example but no, I only have a user shepherd instance.
<jonsger>apteryx: thx, hopefully I can close reports in the future myself. It worked before...
<antidoto>apteryx: I really didn't understand what you mean. My knowledege in gnu/linux services, and even more in guix is extremely limited. I did guix install mcron and had the same result. After guix remove mcron, running mcron now shows the same message as above.
<apteryx>antidoto: I just meant that I thought I had mcron examples of my own to perhaps help you with, but sadly I don't have any.