<Kabouik>Is extracting a pre-built binary from a tarball a valid way to package something on Guix? Of course it's not ideal but I don't know if it would be accepted or not. Asking for this (https://github.com/darkhz/bluetuith/issues/7), where the dev is already deep in the rabbit hole trying to package their application while a prebuilt binary would work relatively easily.
<Kabouik>I think the issue they faced jpoiret was (1) the usual rabbit hole of extra dependencies to package, some of which probably depending on some other stuff, and (2) our version of Go being too old for some
<Kabouik>So they tried to work around this but hit other roadblocks. The pre-built binary works fine on my end so I'm kinda happy, but Bluetuith really fills a niche (a nice and fully functional bluetooth manager from the terminal) so I thought it could be beneficial to have it promoted in "guix search" for those that don't know it
<davidl>jpoiret: Hi, I finally saw your tips re Full disk encryption with grub-efi and LUKS2, but Im still not certain how to deal with if you don't use EFI. I just have 1 partition encrypted and use the "regular" grub-bootloader. Do you know how this can be solved for me?
<jpoiret>it depends on whether you want to use a modified grub
<jpoiret>i've written a patch for GRUB that will make it work
<apteryx>I even 'wipefs -a /dev/sdg' and recreated the partitions, but it's still showing a 'my-root' ext4 in blkid for /dev/sdg1 although it should appear as FAT32 with label ESP
<lechner>how about echo 1 > /sys/block/sdX/device/rescan (X is the device letter)
<apteryx>still the same: /dev/sdg1: LABEL="my-root" UUID="76954008-06cf-4b91-b0bb-316d8bab0576" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="626af13c-01"
<apteryx>I'm also in the process of downgrading the Btrfs RAID for the ssd pool from RAID10 to RAID1, so that to keep the data we'll need to keep just 2 drives instead of 5, but this takes a lot of time too
<apteryx>rekado: to be clear, if someone is available, unplugging and replugging the spinning disk which is in the PERC H730P: sdg 0:2:0:0 disk DELL PERC H730P Adp 4.30 00b47dec29951f722100047215604609
<apteryx>I'm still not sure when/how to use serialize-text-config
<apteryx>it seems I need to apply its result (a gexp) to mixed-text-file anyway?
<apteryx>OK, I think I get it. text-config is line-oriented, while mixed-text-file isn't
<jpoiret>davidl: it's building right now, i'll keep you updatde
<apteryx>so hmm, the text-config type is strictly for a list of file-like objects? I thought it could be just strings too, e.g. (list "[Section]" "key1=value1" "key2=value2" ...)
<apteryx>abcdw: any clue as to what text-config is useful for, or examples? I think this got added to support (guix home), if I'm not mistaken. I tried using it with a simple string-only example as shown above, and serialize-text-config doesn't seem to work on that.
<mitchell>I am writing a guile application and I want to use (guix records). How should I specify my manifest so that only the guix guile modules get installed but the guix binary does not. Or am I thinking about this the wrong way
<rekado>mitchell: you can’t slice it. The ‘guix’ package contains not just the Guile modules but also the scripts.
<mitchell>That's a bit annoying. The guix that gets installed will shadow the one made from guix pull. Perhaps it's not a good idea to make guix a dependency just for the records api
<abcdw>apteryx: it was reworked and now it's pobably accepts a list of strings or file-likes and the content get concatenated with \n, so you can write something like (list "alias super-ls=ls -with-options" (local-file "./my-old-bashrc") ...)
<apteryx>abcdw: now as in its current state in master?
<apteryx>if so, I wasn't to make use of it with pure strings, because 'serialize-text-config' does some with-input-from-file on strings... which are not files, and fail.
<jackhill>Is berlin still down? It looks to be working (at least in some degraded state) for me
<apteryx>there may be an odd substitutes missing while things get sync'd
<apteryx>I need some extra eyes with a new dconf-service-type that I'm using here: https://paste.debian.net/1254670/ to support a new 'auto-suspend?' gdm-configuration option. Currently, it doesn't seem to extend at all, /etc/dconf doesn't exist in a VM
<apteryx>and guix gc -R /gnu/store/path-to-run-vm.sh | grep dconf doesn't have it either
<apteryx>so something is probably badly defined for the extend or compose of dconf-service-type, I'd guess
<Guest3>I know where it's defined, but the output of the `desktop-services-for-system` function changes depending on the system
<Guest3>the function ran when I did a `guix system reconfigure config.scm`, and I want to know what it's output was, maybe it's stored somewhere, maybe I can re-run the `desktop-services-for-system` fn
<jpoiret>Guest3: you can load your file in a guix repl and inspect the resulting operating-system object
<jpoiret>ie (define os (load "my-config.scm")) then (operating-system-services os)
<Guest3>hmm, outputs a lot of stuff (fills my screen), how do I parse the output?
<jpoiret>you can explore it with things like (for-each (lambda (service) (format #t "~a~%" (service-type service))) (operating-system-services os))
<podiki[m]>all I know is that at first opening it I see a huge list of channels (I assume) most of which do not make sense for one that knows nothing of rust....but thanks, will ask there if I don't figure something out later
<lechner>hi, i use setuid-programs for opensmtpd to mark the executable mail tools setgid, but the new gid appears to be effective only for users but not the smtpd daemon itself. as a result, smtpd is unable to use 'sendmail' to process the offline queue (I am not sure why it needs to use sendmail). has anyone seen anything like it?
<apteryx>podiki[m]: there's an issue in our bug tracker somewhere to better handled killed processes but I can't find it
<abcdw>But original implementation of text-config, which accepted strings or gexps, could be combined with slurp-file-gexp like this: (list "# bashrc preamble" (slurp-file-gexp (local-file "./bashrc-old")))
<abcdw>However, Ludovic mentioned that slurp-file-gexp maybe problematic in some case, I still not sure in which.
<podiki[m]>apteryx: okay. so will want to add an ignore to that function and note in the package def that this is due to SIGINT handling (so one day someone will fix these)
<apteryx>ah, SIGINT is different than what I had on mind (zombie processes). I think it happens sometimes when the tests expect an interactive terminal to be connected to the application.
<podiki[m]>so end result is test relying on SIGINT need to be skipped though? (like in python-uvloop)
<podiki[m]>I'll quit after the various patch phases to see if the substitute looks good, since honestly that's where I would go wrong (though this looks easier than most substitutes)
<jesse`>Hi all. Guix recently upgraded my kernel (using `guix pull`) to 5.19, which I found out does not work well with my system. I see the definition of the 5.18 kernel is now gone from linux.scm, so I was wondering, is it possible to keep using the 5.18 kernel and still upgrade the rest of my system?
<podiki[m]>well there's also other versions (like 5.15) if you want