IRC channel logs
2026-09-25.log
back to list of logs
<ryanprior>could be added by a bot? or maybe it's possible to be added to the organization without being a committer? <new_user>It took a long time, learning minute things about LaTeX, XeTeX, Kpathsea, but finally I learned that I needed to set the environment variable GUIX_TEXMF pointing at the directory containing the TDS (usually called "texmf", but here called "texmf-dist"). <new_user>So, GUIX-TEXMF is to Guix's TeX Live what GUIX_PYTHONPATH is to Python. <apteryx>is the need to manually invalidate .go files a specific issue introduced by the Guix syntactic records? Or something generally true in Guile, because Guile is not smart enough? <apteryx>I don't currently recall another time I have to do this other than because some guix record changed... <jlicht>apteryx: would v8-disable-temporal-support not help if the temporal-capi stuff is an issue? <apteryx>jlicht: indeed; from Node's BUILDING.md: "Pass `--v8-disable-temporal-support` to opt out of Temporal support and remove the Rust toolchain requirement." <jlicht>apteryx: why would I read well-written documentation, if I can just grep random build scripts and hope the options do what I need them to do ;-) <apteryx>jlicht: maybe because that's often the only way, ah! <jlicht>apteryx: perhaps our approach has hit the end of the road; the npm/node community is very sceptical about trying to use npm in any "non-default" way <apteryx>they wouldn't be the first skeptical people we encountered to be fair <jlicht>but it seems to check the npm endpoint itself on the registry; could be some auto-update setting that we don't have. Can you try setting the "npm_config_update_notifier" env var to FALSE? <apteryx>jlicht: thanks for the idea, I'll look into it when I context switch back :-) <jlicht>apteryx: I'm still sitting on some node-build-system "improvements" (sidegrades?) that do this already <apteryx>jlicht: tried the npm_config_update_notifier=FALSE trick, to no avail unfortunately <jlicht>sounds more like an arborist thing tbh <abrenon>I'm pretty sure I saw it somewhere but I can't find it anymore: what's the way to find packages depending on a given package? <abrenon>must be something with guix graph possibly? <jlicht>apteryx: it works for me, fyi. With my build system changes <jlicht>which I expected, as I "properly" link the tree of deps instead of having the (faulty) hoisting <jlicht>So I'll brush it up somewhere today and then you can be unblocked <jlicht>and have you be my first alpha tester ;-) <apteryx>oh wow! I'm looking forward to test it :-) <apteryx>abrenon: guix graph --path package dependency <cbaines>apteryx, using that requires some guessing, that only verifies the link, you'd need to run it for all packages or guess the ones that abrenon is looking to find <abrenon>apteryx: cbaines: exactly, I want to discover <apteryx>ah, right. then I think you'd have to use fold-packages <abrenon>I reported something about zenity, I noticed it from wl-color-picker but I then wondered if some other packages could have zenity as dependency <abrenon>I thought I once saw something like that in the codeberg template when one opens an issue <abrenon>but I can't find it anymore sorry :( <abrenon>apteryx: what's this fold-packages? is it a function in guile? <apteryx>it's a Guix API, from (gnu packages) <abrenon>well I found other packages among which mepo, sbcl-messagebox and winetricks! thanks for the tip of using fold-packages <avalenn>read-with-comments from (guix read-print) chokes with gexp #~ when I try to use it in a personnal script <avalenn>ice-9/read.scm:126:4: In procedure read-expr*: ex1.scm:8:9: Unknown # object: "#~" <avalenn>I must miss something on how this must be used but it seems to me it should work <Deltafire>i need librewolf to start with MOZ_ENABLE_WAYLAND=1, preferably setting it in the stub. I guess I'd have to create a new package definition for this, inheriting from the current librewolf package? <avalenn>answering to myself : I needed to import (guix gexp), probably to activate read-hash-extensions <jlicht>Deltafire: afaik this is no longer required <Deltafire>the problem i'm having is that without that set, librewolf won't start if XAUTHORITY is also unset <apteryx>that's a current bug in gnome-session-shepherd/GNOME 49 on Guix System <n|Phreak>Has anyone looked into docker containers to guix containers ? <n|Phreak>I haven't searched a lot on the subject yet , just curious if anyone else has ? <untrusem>so mean a import like feature for oci definations? <tusharhero-xmpp>I think I saw something like that in guix system image options untrusem <n|Phreak>no basiscally take a compose file and try to convert to a guix container I guess <untrusem>n|Phreak: yep that's what i thunk you meant <untrusem>in theory yes you could do that, basically you need to write a importer/converter or something <n|Phreak>wonder if it would be worth it , just seeing if a guix container would be less resources or not <untrusem>it will be using podman or docker under the hood anyway <apteryx>guix container does not use podman or docker; it uses clone(2) from linux :-) <apteryx>(which podman and docker must be using too) <untrusem>I am messing up guix container and guix shell container <n|Phreak>I updated all my systems , only issue is that you need to put ;;; -*- lexical-binding:t -*- on all headings now <untrusem>n|Phreak, do tell me after you compare guix and docker containers <n|Phreak>ACTION untrusem , I was thinking you could do it and then tell me (: <untrusem>I know some friends who use the oci service, I will ask them <tusharhero-xmpp>I think undesirable to hardcode gnu store paths in desktop files(?). I use the dino client for XMPP, I didn't like somethings about so I had patched it with package transforms. The patches work fine when I start dino from bash, but when I open it using the GUI icon it opens the unpatched version. <tusharhero-xmpp>(it opens the unpatched version because the gnu store path is hardcoded into it) <ieure>tusharhero-xmpp, It's standard practice to put store paths in .desktop files. You usually have to log out and back in for the DE to pick them up after you install or reconfigure to bring in a new or updated package. <ieure>Just noting that people use Guix different ways, some use `guix install' with a per-user profile, others use Guix Home, which you `guix home reconfigure'. <ieure>So whatever action corresponds to how you use it. <ieure>Log out / back in should solve it. I've noticed that Plasma seems to cache .desktop stuff more aggressively. <ieure>So it's either that or a bug in the XDG cache stuff. <lechner>I think that sets the path to the correct GUIX_ENVIRONMENT every time. <sh>If I install a package for root and user, and does it take up twice the diskspace? <lechner>No, but your two Guix executables must be sufficiently similar. <rho`n>From my understanding the store (/gnu/store path) is where the package derivations that have been built successfully are stored—by default. So as lechner says, if two users reference the same package version, then there would be no extra disk space used. <untrusem>sh, if you install a package for root it should be automattically available for the user <untrusem>kestrelwx, I will ping some committers later