<attila_lendvai>sneek: later tell civodul: respawn-service in shepherd doesn't seem to check whether the service is disabled or not. i got into a state where my service was stopped according to `herd status`, i also issued a `herd disable`, but the process is still running, and whenever i terminate it with a kill -TERM, shepherd keeps respawning it.
<ryan77627>...wlr's portal, however after the main build phase, i need to build a secondary component. Is there a way I can `cd` using guile in the build environment? I'm already making a new build phase after the default one to build this secondary component and am planning on using a lambda, but would just running "cd" in it as well work? Not too sure the "proper" way of accomplishing this
<ryan77627>jackhill: Wow, you had that on lock and ready to go. Thanks, I'll take a look!
<jackhill>ryan77627: haha, I've had need of it as well :)
<jpoiret>ryan77627: doesn't wlr support hyprland as well?
<matto->newbie question: is there an example how to setup your .emacs-file, while using emacs-packages through the package manager, like guix install emacs-smartparens, and so on? On other systems I use (use-package ..), should I do that on Guix too?
<zamfofex>ryan77627: I was trying to package Hyprland the other way, but it seemed difficult, because it required some foundational Wayland and general GUI packages, and it seemed to need to rebuild a lot of stuff.
<jpoiret>csepp: did you update your system and user profiles as well?
<jpoiret>we never managed to get to the bottom of this specific issue, most of the time upgrading all profiles would solve it. I think one library isn't in the shell and gets picked up from the system-wide profile, which is linked with an older libc
<Parnikkapore_m>I might be trying to package something that requires downloading two separate source tarballs. How do I do that?
<mekeor>Parnikkapore_m: wildly guessing, write a package for one source, and use it as dependency in the other package :D
<attila_lendvai>Parnikkapore_m, i think i've seen somewhere an origin entry in the inputs
<mekeor>it'd be nice if there was something like ripgrep for s-expressions
<janneke>Parnikkapore_m: with gexps this has become easier, grep for '#$(origin'
<Parnikkapore_m>I knew there's gotta be a really easy way to do it with gexps haha, thank you so much!
<f3n1x>hi guixers ! ... newbie here. I work with hugo web framework. I've downloaded it as a binary. Placed it into '/opt '. The /opt/ folder is in my $PATH by means of ~/.config/guix-home/.bashrc . When i run 'hugo' it doesn't work though . What am i missing ?
<johnabs[m]>Hi all, I asked here recently about an issue with building xmonad and ld not being able to find librt due to an update in glibc (I think) and the subsequent gcc-toolchains. Has anyone else managed to find a way to deal with this, per chance?
<pkill9_>im running guix on fedora, and when i run quasselclient from guix it doesn't use a dark theme whereas native fedora one does, i'm wondering what might be causing it not to do so, anyone know why this might be?
<pkill9_>oh, it needs qt5 style plugins i think, which appear not to be packaged in guix
<johnabs[m]><HiltonChain[m]> "The packaged xmonad has substitu..." <- It's possible I'm using the incorrect terminology: I have the xmonad substitute installed; however, I need to run xmonad --recompile to get my configuration working every time an update is installed. For this, it requires both xmonad, (and xmonad-contrib), but also gcc-toolchain to build the new file that is run when xmonad is called. For right now it is "working" but none of my
<johnabs[m]>configuration settings are reproducible, and when I try to rebuild my config, I get the error from ld that -lrt is missing. I hope that clarifies things, and that it makes sense :)
<HiltonChain[m]>librt is from glibc, can you try again with this package in you profile?
<lilyp>Is there a magic trick in guix graph to cut the graph at a certain point?
<foxfromabyss>hey :) i have managed to install emacs 30.0.50 with tree-sitter on one of my devices with GuixSD. But I can't manage to reproduce the installation on either of the devices for `emacs-next-tree-sitter` and end up getting 29.0.91. Am i missing something?
<johnabs[m]><HiltonChain[m]> "librt is from glibc, can you..." <- Right, so what happened was that librt was merged into glibc, and now LD can't find the librt.so.1 files (I think, jpoiret and I discussed this a bit) but the problem is that now all gcc-toolchain versions available rely on glibc 2.5 (I think) so even if I install the new version, would gcc-toolchain be able to see that correctly?
<lilyp>mirai: again, the point is not to write out "arguments" but to give it a quick and snappy name that needs no abbreviation
<cwebber>got a pinetab2 and didn't realize we were ordering something so *brand new*! I wonder how hard it will be to get guix running on it... I'd definitely love to run Guix on it if I can. I'm not sure if the pine64-image-type works with the quartz64
<cwebber>I guess I'll give it a shot and see what happens
<VesselWave>Guest28: You should have a path relative to what you specify in -L. So if your file is ~/dir/dir2/dir3/file.scm and -L is `~/dir/dir2`, you should have (define-module (dir3 file) on top of the file
<mirai>though I don't see why it would be relevant since apply is guaranteed to receive 2 mandatory arguments
<mirai>the serializer-options is the last argument to appear within the (apply …) call
<lilyp>(apply (lambda (field val i-really-need-this-value-tho) ...) "hello" "world" '())
<mirai>I guess you could creatively devise serialize-<type> procedures that take one or none arguments if you tweak the transducers
<VesselWave>Guest28: I guess you should just put (packages test), without my-channel
<mirai>that would raise an exception since the serializer doesn't get what it wants
<lilyp>true, but it'd also be a case of bad serializer design as opposed to optionals or keywords is my point
<graywolf>Hi, just reporting that I got duplicite item in RSS feed of Guix blog. It seems entries were updated and now end with // (...for-gnu-guix//) instead of / (...for-gnu-guix/). Not sure if it was intentional.
<lilyp>if you have a serializer with a mandatory third argument, you basically always have to provide that argument with next to no real indicator that you can do wrong at compile time
<mirai>perhaps I'm misunderstanding but what scenario should be covered with a test as well?
<lilyp>Test 1: (lambda (field value #:optional something) ...)
<lilyp>Test 2: (lambda (field value #:key something) ...)
<lilyp>Test 3: (lambda (field value #:optional something #:key some-other-thing) ...)
<lilyp>for instance, section specifiers in ini fields could easily be #:optional
<mirai>What is to be tested here and where will this take place?
<lilyp>whereas quoting styles and other fluff could be #:key (there are different ini formats out there)