<Ribby>Turns out that few moments became a few hours short of a day! Maybe around 12 hours plus a schedule?
<Ribby>There's a bit of speckering in net stability and blank/sleep screen interruption during update/pull and upgrade, but so far things looking up.
<Ribby>I got the package extraction down, but now how do I make it install a program? I was just going for the flathub, but apparently, no guix support? Should I just pick a choice? Source code compilation is another time, I couldn't find the dependencies anyways (I am not the said project developer anyways).
<Ribby>Hold on, I'll restart because it's usually a norm for updates.
<lilyp>okay, then I hope I'll have some more time after they're done
<phf-1>gnoo, lilyp I'm ok with not running the tests. The idea is to contribute the package to Guix and so, maybe it's worth it to try to make the tests work. If it's ok not to make the tests work then I can send it to Guix with #:tests? #f maybe.
<gnoo>phf-1: try sending with #:tests? #f and explain why the tests are disabled. i think they recommend to always to the test but if it's a hassle setting that up then...
<gnoo>maybe there's some other postgresql-related package that runs similar tests?
<davidl>make a quick fix? mbakke: this also causes a problem in the create script of ganeti-instance-guix leading to failures with the qemu-img command therein which copies the guix system outputted image to the target device ("cannot grow device file" or similar).
<davidl>root@node2 ~/src/ganeti-configs# echo 'thus we can do this: DEVICE_SIZE=$(( DEVICE_SIZE - $(( $(( 2**20 * 40)) + $(( 512*2048)) )) )) directly after setting DEVICE_SIZE in the create script in ganeti-instance-guix'
<mbakke>davidl: subtracting the EFI partition size from DEVICE_SIZE seems like a good workaround for now, would you like to submit a PR? I can relase a hotfix version with it.
<davidl>Yeah, I can submit by tomorrow probably is that fine? I have to leave my computer about now.
<civodul>dlowe: in terminals that support hypertext links
<civodul>so not xterm, not Emacs shell-mode, but something like GNOME Terminal
<dlowe>okay, I don't get hypertext links here, just /gnu/services/mail.scm:lineno/colno
<civodul>looking at the code, that part should be a hyperlink on terminals that support it
<tschilptschilp23>Is it fine to have 'guix system' and 'guix home' at different states (guix home at a newer state than system, by means of 'reconfigure' calls)? I'm asking because I just had some strange gnome-behaviour, that somehow seems to have been solved by a system reconfiguration...
<abcdw>tschilptschilp23: In most cases yes, I even have different channels for System and Home.
<tschilptschilp23>abcdw: basically my programs were running, but I couldn't use them, because in not-overview-mode I had this grey 'oops, something went wrong that couldn't be resolved by the system, please logout and try again' fullscreen-window covering everything else!
<tschilptschilp23>abcwd: I will have an eye on that. They were some 9 pulls apart from each other because I was changing a lot in Home and forgot a bit about System :)
<jpoiret>TIL macOS has a sandboxing feature that can restrict access to filesystem/network and other things!
<form_feed>I'm working on a system configuration for my first Guix real installation. I want a LUKS>LVM>BTRFS setup. In the manual, I see that the `swap-space` declaration accepts a `dependencies` list, but I see none for `mapped-devices`. My question is: is it enough to have the `mapped-device` declarations listed in the expected order to indicate a dependency? So `(mapped-devices (list (mapped-device LUKS)
<form_feed>jpoiret: Well, the short answer is that this needs to be a bulletproof "work" system and, at this point, I'm not sure if I'll be able to get Guix the way that I need in time. So I'd like to ensure that, if needed, I'll be able install something else quickly to get something done before I resume my migration to Guix. I like the flexibility LVM gives me there.
<jpoiret>right, just saying that subvolumes can achieve the same here
<jpoiret>as an example, I had /guix_root and /arch_root on my btrfs partition
<form_feed>With multiple distros? Oh, never saw that. O_O
<jpoiret>with 2 completely different systems on them while I was moving to guix
<jpoiret>basically, you mount the same partition but with a different root
<jpoiret>right now, my home is the subvolume at /arch_root/home while my root is /guix_root
<jpoiret>(meaning my guix root is both at / and /btrfs/guix_root)
<form_feed>That sounds really good. Makes sense to move the root from / to something named. Thanks for this tip!
***jonsger1 is now known as jonsger
<KE0VVT>I forgot the env. var. that makes Alacritty work on the X200.
<jgart>Hi Guixers! Is this something I can ignore when compiling Guix? "Please consider running po4a-updatepo to refresh it."
<unmatched-paren>hello guix; i've been meaning to do this for a while, but was scared off because last time i did it, i bricked everything and now i've forgotten; how would i remove GDM without removing the whole of %desktop-services?
<podiki[m]>jpoiret: presumably such a thing would be useful in other ways, when you need a file-system reference (I don't know what, but seems like something that should be available in the configuration system)
<phf-1>podiki[m], It's very much in flux. Trying to centralize all the inputs I get from the channel and aggregate them somewhere.
<unmatched-paren>it made a horrific scratching noise when it tried to suspend and as we've just seen corrupted it
<rekado>phf-1: in the past we have repeatedly added articles to the cookbook that had previously been published as blog posts.
<phf-1>rekado, Ok, so how can I send you that post?
<rekado>phf-1: depends on how involved you’d like to be :) Ideally, we’d receive any addition to the cookbook as a git-formatted patch to the guix-cookbook.texi file.
<rekado>but if you think that this is too difficult to accomplish you can also send your article to email@example.com with a subject that indicates that this is meant to be an addition to the cookbook.
<phf-1>rekado, Ok. Will try the texi file path first. Maybe org-mode can be exported to that somehow.
<ngz>phf-1: Org mode can export to Texinfo, indeed.
<podiki[m]>jpoiret: nice! personally I'm okay with plenty of code, but would it make sense to not have the "filter" needed explicitly in the configuration? so (file-system-mount-point "/btrfs" file-systems) instead, where that function incorporates the filter?
<podiki[m]>or are you thinking for other uses for that predicate?
<jpoiret>that's what i thought initially too, but i think it's just as readable and lets you see filter in action