IRC channel logs

2025-08-15.log

back to list of logs

<Kabouik>My low performance device is pulling Guix channel and stuck at the step "executing builder `/gnu/store/hd8l10rk924x8c48h9w6a8b0gp5iydzx-guile-3.0.9/bin/guile'" since quite a long time now, and I'm already at --debug=3. Is there some other flag I can try to enable to have more feedback of what's happening and taking this long?
<Kabouik>The CPU doesn't even seem to be under load.
<decfed>how do you do bind mounts? I have trouble following the example in the cookbook: why are the path defined as thunks instead of variables in that example? In my case I want to bind mount a path on a luks device, so defining the file-system outside the OS definition causes headaches when referring to the mapped devices as dependencies of the file system. Any ideas?
<Rutherther>decfed: you might have easier time to use the vfs-mapping service https://guix.gnu.org/manual/devel/en/html_node/Linux-Services.html
<csantosb>Good morning, Guix ! I'm trying to understand how .go compiling works ... If I do a `make -j8' in master, I get all of them; making again does nothing, as expected, great
<csantosb>Now, I change to any other branch; do nothing at all, switch to master back again
<csantosb>Make ... restarts the .go dance again ... Am I doing something wrong ?
<csantosb>This is endless and frustrating
<ekaitz>csantosb: if it was a C project with .o files, what should happen?
<identity>csantosb: well, git changes mtime on the .scm files, so guile recompiles them; i think git has an option to set mtime of the files to the commit timestamp, though it will likely cause more problems with stale .go files…
<csantosb>ekaitz: No idea. I'm mostly vhdl.
<csantosb>identity: no turnaround then 😥 ?
<ekaitz>csantosb: use worktrees
<ekaitz>they help a lot
<ekaitz>or do as I do: always work in master (hehe)
<csantosb>I'm using worktrees ... except at every new worktree, you need to recompile everything from scratch; I'm getting paranoid about .go files
<ekaitz>but when you move back to other branches, if nothing changed you shouldn't need to recompile
<ekaitz>csantosb: the main problem is if the files are modified or their modification time changes
<ekaitz>that's what `make` checks
<ekaitz>as identity was saying, when you checkout anything from git, it rewrites your folder with the files from the `git` database
<ekaitz>and that changes the modification time -> and fucks you up
<csantosb>I know ... just wanted to be sure that I'm not heating the planet for nothing ...
<csantosb>... a little trick to avoid that or something; no hope ...
<ekaitz>don't checkout, that's the trick
<ekaitz>if the problem is that you change a lot from one branch to another, try to avoid that
<ekaitz>keep them separate and compiled
<ekaitz>so you only have to rebuild things that you changed
<ekaitz>in any case, i think the guix model of recompiling is not a very good fit for our project, because we have large files that change often
<csantosb>Are there alternatives ?
<ekaitz>csantosb: idk
<jakef>when i run this script https://0x0.st/Krcs.txt, i get 'guix time-machine: error: Git error: failed to connect to git.guix.gnu.org: Operation timed out'
<Ingarrr>Hey, quick question: what are the naming rules around the same package, but a released version vs. the latest from git?
<Ingarrr>I have seen things being suffixed with '-next', is this the way to go? And should it only be in package-variables, or also the package name? or in the package version?
<jakef>can you think of a package like that already in guix?
<identity>Ingarrr: ‘-next’ is generally the way to go, it should go in the variable name and the ‘name’ field of the package, the ‘version’ field should be the usual for git packages, constructed with the ‘git-version’ procedure
<Ingarrr>thanks!
<untrusem>Would I be able to change the NFTables rules on a running system?, because it needs a system service and I don't want to reconfigure every time I change the rules
<mange>I think you can restart the nftables service after reconfiguring the system. It looks like that will run "nft flush ruleset" then "nft --file $your-ruleset" (whatever that does).
<untrusem>ohh
<mitchell>Hello Guix, I stumbled upon this mail thread https://lists.gnu.org/archive/html/guix-devel/2024-05/msg00158.html so by popular demand I added some ZMK love to https://github.com/paperclip4465/guix-zephyr/blob/master/zephyr/zephyr/packages/zmk.scm
<mitchell>However I do not have any of these keyboards so if anyone does and would like to test it would be much appreciated
<untrusem>mitchell, you should also announce it on fedi with #guix hashtags, there might be people that needs this :)
<untrusem>can I define my own system keymaps?
<mitchell>I'm not sure. If that is done via the config/ repository then yes.
<mitchell>how do i announce such things? I am really not a good internet user haha
<untrusem>lol, just share what you shared here, :p
<mitchell>what is fedi?
<untrusem>ohh, wait a min
<identity>mitchell: fediverse, but untrusem probably means mastodon specifically
<untrusem>mitchell: if you can bear watching a video, this introduces fediverse https://videos.elenarossini.com/w/64VuNCccZNrP4u9MfgbhkN
<mitchell>hmm. I don't have any social media. Is there an easy way to get started with it using guix software?
<mitchell>preferably something that doesn't have a timeline or trending feed
<untrusem>if you use emacs, of course you do, :p there are emacs clients for it
<identity>mitchell: well you probably do not want mastodon then, it is a twitter clone… you might want to post that on the guile-devel mailing list, if you did not do that already
<mitchell>ah, emacs mastodon seems to fit the bill. good ole emacs, the last bastion of user friendliness
<identity>er, guix-devel
<untrusem>identity: you can disable real-time timeline I think
<untrusem>I don't know if mastodon.el supports it or not
<untrusem>You can just disable real time` updates, not timeline, yeah then mastodon is no good
<mitchell>It's alright, the website interface is good enough.
<untrusem>👍.
<csantosb>Codeberg is down now ?
<mitchell>It seems so
<untrusem>yep
<untrusem>another ddos?
<untrusem> https://status.codeberg.org/status/codeberg
<mbkamble>Hi. I have used a guix system on my Dell XPS 13 6 yr old laptop for almost two years. So I am familiar with the system configuratio, channel spec etc. and have regularly done system upgrades using "guix pull". But in the last couple of weeks, eeverytime I do "guix pull -C <mychannels.scm>", the upgraded guix crashes with a SIGSEGV fault. The last
<mbkamble>good guix that works for me is commit 93d10b5f4e709ed8d6f95f63f1279f52fd982ea8 (from around Jun 27 2025). I have searched for a solution and experimented a lot, but unable to resolve this issue.
<mbkamble>Any help to eliminate will be gratefully appreciated. If any additional info is required, I can share it via pastebin
<ieure>mbkamble, I've seen at least one other person mention this problem, do you want to file a bug report on Codeberg, or ask on help-guix?
<mbkamble>i see. yes. I will post a message on help-guix
<kkremitzki>Codeberg status update: https://social.anoxinon.de/@Codeberg/115033790447125787
<ieure>I utterly despise so-called "AI."
<kkremitzki>Yeah, it's extremely annoying, I also maintain the FreeCAD project infra and I lost many nights and weekends to fighting fires earlier this year, solved by Anubis but apparently not for much longer
<eikcaz>Could someone share a hetzner deploy example config? I'm trying to use the minimal example from the docs, but I get "guix deploy: error: machine: source expression failed to match any pattern".
<eikcaz>s/docs/guix user manual/