<jbnote>ulfvonbelow: following your earlier hints, i've replaced (string-append (file-append ...)) with a mere #~(string-append #$(file-append ...)) and it works :/. Do you know how I would go about understanding where the object is stored and what happens? I'm writing a system configuration. I've tried to trace the derivation that produces the file (-nginx.conf.drv), got as far as -nginx.conf-builder, which is a guile script, but everything
<jbnote>has been expanded at this stage (correctly or not).
<jbnote>ulfvonbelow: In any case, thanks a lot for your help. I'm not at a level where I can understand what happens, but at least you gave me a workaround.
<ulfvonbelow>well, for starters, where is your #~(string-append ...) form appearing? Is it in a field definition?
<TehBassalt>i managed it using emacs shell, but it gave an error since just the first bit didn't include all of what operating-system needs
<ulfvonbelow>I suppose you could, in an editor of your choice, copy+paste the config file up to that point into a separate file (or comment out everything after that with semicolons) and then run (load "/path/to/config.scm")
<ulfvonbelow>ah good, if you have an emacs that makes things quite a bit easier
<ulfvonbelow>so the error doesn't occur prior to the start of the 'operating-system' form?
<ulfvonbelow>in the former case, you would have top-level defines for your mapped devices, and for each of your file systems, and then in your 'operating-system' form you would just have (file-systems <your-filesystems-variable-here>) and (mapped-devices <your-mapped-devices-variable-here>)
<ulfvonbelow>TehBassalt: I believe all non-root filesystems implicitly depend on the root filesystem. My guess is that because of this it's not creating a shepherd service for your / filesystem, but not preventing the shepherd service that it creates for your /home filesystem from depending on it
<ulfvonbelow>I think removing the root file system from the list of dependencies might resolve it
<TehBassalt>i'm not sure, i've just let it go with only the dependency on mapped-devices
<civodul>apteryx: ah yes, ok; it’s deleting a bit too aggressively, but i’m not sure what a good middle ground would be
<civodul>we can keep it that way until we have a better idea
<panosalevro>hi all. my neomutt+getmail+procmail setup doesn't work properly on guix. when fetching emails, procmail complains that "/var/spool/mail/user" can't be created. any ideas?
<stocastico>hello :) how would I go if I wanted to implement a new kind of "lowerable" object? I'd like to have a new kind of record that I can build with guix build -f object.scm. Should I look into local-file, computed-file and co. implementation? Or is something on a lower level required in your opinion? Thank you :)
<bjc>panosalevro: guix doesn't have ‘/var/spool’; you could ‘mkdir -p /var/spool/mail/’ and see how it goes. you may have to touch and chown the mailspool, though
<bjc>alternately, tell procmail to use a different location, like one in your home directory, and configure mutt to do the same
<apteryx>civodul: on the flip side, it exposes bugs we'd never or rarely catch (missing gc roots)
<apteryx>I suspect that missing drv bug may be related
<apteryx>hm, emacs-debbugs seems to hide feature requests by default; how can I show them?
<apteryx>ah, add 'wishlist' to severities when prompted i guess
<RavenJoad>Does Guix's packaged version of KDE work on Wayland? Or is only GNOME & sway meant for Wayland right now?
<luke-jr>now that I have a recent-ish Guix going, can I build the official 1.4.0 iso?
<panosalevro>after upgrading, dolphin won't run. i get this "/home/user/.guix-profile/bin/dolphin: error while loading shared libraries: /gnu/store/5h0hzz9isvwr4lfxfa8ls13dyvi1z2a5-baloo-5.108.0/lib/libKF5Baloo.so.5: file too short"
<pastor>hi. A quick question. If I'm submmiting an update of a package which requires to add a new package on other file, how should I submit it? In this case I need to update the definition of the `notmuch` package on 'gnu/packages/mail' and I add a new package on 'gnu/packages/c' to support the update. Should I do a patch series?
<pastor>The c package is a library that's required for the updated `notmuch` definition.
<lilyp>yes, you should do a series, with the first patch adding the library and the second updating notmuch
<lilyp>unless it makes sense to do so, don't simply add the library in the same file as notmuch; instead aim to find the "best fit"
<mirai>lilyp: Is #66407 still on time for the gnome-team branch?
<graywolf>Hi Guix :) I want to write a service that adds an service and I am unsure how. I assume some extension, but what? (service-extension WHAT-GOES-HERE? nftables-service-type) ; Any tips or (even better) examples?
<civodul>sneek: later tell mothacehe commit 373ec2cf8ce97d5f89191c3d9211ee3a5c2067dc lacks the actual pack.scm change no?
<civodul>that’ll show you how service types extend one another
<graywolf>Ok, will try that and come back if I still don't undertand :)
<jbnote>so, what code hosting platform should a good guixer use: sourcehut or notabug?
<jaeme>jbnote: sourcehut requires users to pay a fee for hosting repositories, codeberg is also a good option. In terms of freedom, i guess pick the one that works with LibreJS the most.
<podiki>and possibly set to mirror on others for maximal coverage (backup and discovery)
<luke-jr>will guix time-machine try to downgrade my (customised) guix-daemon?
<lilyp>mirai: it still is; QA hasn't applied it, same as with my recent submissions
<lilyp>if you mean "on time" with the 44.6 oldstable release on sunday, don't sweat that; I'm not sure whether we'll be having a functional gnome-team branch by then
<graywolf>civodul: Hm, I have to say I am not really any wiser from the extension-graph output. I think I have some grasp on how the extending works. And there is profile-service-type for packages. But I do not see service-service-type for services.