IRC channel logs
2026-09-07.log
back to list of logs
<apteryx>note to self; when debugging why the generic html updater can't find a release, instrument import-html-updatable-release <apteryx>other note to self; this is a place where having logging would greatly help <TheTaoOfSu>Does Guix have much impact on RAM usage? I'm considering using it for a server, but it's going to be pretty low resource, 1-2 GB <apteryx>most intensive resources usage like cpu and ram is when running 'guix pull' (or building packages locally) <apteryx>in normal system operation it stays out of the way; with perhaps its pid 1 using some extra 30 MiB for the guile VM than say, systemd <apteryx>(assuming you meant running Guix System) <apteryx>I use it on a 2 GB vps without any problem; when you use 'guix deploy' it'll build most things locally, so if your local machine has better specs, it'll be fine. <coopi>gcd001 tells to announce new submitted gcds <coopi>coopi does not have the ability to post there <coopi>(its mail gets rejected since its no maintainer) <coopi>apteryx: hmmmm, coopi had already announced on guix-devel <coopi>does that mean it don't have to do anything further?? <coopi>its been a couple days and no one has replied or even reacted <coopi>so im worried that i did something wrong <apteryx>the info-guix mailing list is very low volume, and most things that is moderated (since nobody ever rarely posts to it) <apteryx>so it needs an attentive human in the loop <jlicht>coopi: just because you're paranoid, doesn't mean they're not out to get you ;) <janneke>byte-code: Loading file /home/janneke/.config/emacs/lisp/guix.el failed to provide feature ‘guix’ <janneke>what happened to emacs-guix, is the question <janneke>so, this (require 'emacs-guix nil t) needs to be changed to <apteryx>hm, rebooted into GNOME 50, but GDM appears to auto logs with gdm-greeter, as if it didn't know about other users. <coopi>jlicht: by 'did something wrong' i meant that i messed up the process somehow owo <coopi>ive already managed to do that once <coopi>its a somewhat long story but due to a comedy of errors i had managed to exhaust six of my 7-day find-a-sponsor deadline cuz i did the announcement process incorrectly / in the wrong order <user220>hello! does anyone know how to set up a different shell that is not bash or zsh? i have issues with env variables... <joostvb>user220: what's the issue? i'm curious <user220>@joostvb env variables are not set... <coopi>user220: what shell are you using?? <coopi>which does not source /etc/profile and hence does not set up the environment variables <coopi>by spawning the POSIX sh to capture and return the environment which i then import into the main shell <untrusem>did you find sponsors for your gcd? I can do that if not. <coopi>alsu no worries about the gcd, i found sponsor <coopi>hope u get well fast meaow :c <coopi>user220`: if there were a neater way, i wouldve been using it instead :p <coopi>this workaround is so far the most elegant solution ive found <coopi>and it works perfectly fine for me <user220`>@coopi just to clarifi when i say shell i mean what shows up right after login... <empathy_monster>Just checked the irc logs. Thanks so much cellarweasel for the info for the guix-install.sh script. Works like a charm! <empathy_monster> It's been quite a while since I've run guix and I'm going through the docs rn. Curious if there's a way to distinguish between a native binary and one from guix? Bc atm my system seems to favor anything installed by 'guix install' and native binaries, say in /usr/bin/, take a backseat <bremner>Is the need for a local keyring branch documented somewhere? I saw some mailing list discussion from 2020 but I don't really understand what the issue is. <coopi>im referring to the login shell <coopi>my workaround applies to that <coopi>theres also an alternative approach, however, where you don't set your desired shell as the login shell at all. and instead, in your bashrc u configure the login shell to immediately spawn your desired shell, thereby inheriting the environment <sham1>empathy_monster: you could just put your guix PATH etc after your system PATH <sham1>You really can't pick and choose <bremner>I guess a less XY question is "how do I run guix system image" with one new commit? <sham1>I guess you could go and add yourself to the keyring branch locally. Then it should work (assuming you haven't done so already) <sham1>And/or have you signed the commit at the HEAD <bremner>although maybe I did the keying wrong <PotentialUser-91>I ran into a kernel regression on linux 7.1.10. I had 7.1.5 before and no problems, now I get nvme timeouts and the system finally hangs. Old kernel generation works though. config.scm is no difference. Anyone else experiencing this? <empathy_monster>I'm still working through the docs. I plan on installing the full system when I have some extra time to devote to it. Rn I'm just running guix pm on top of Arch <empathy_monster>I'm mildly allergic to s-expressions :P so I want to spend more time with guile <mfg>How do I make certain packages extend env vars like C_INCLUDE_PATH? <mfg>Does someone have an example package I can look at on the top of their head? <mfg>Also, how do I add a team? Can non-committers be team members? <cbaines>mfg, as for teams, yes, non-committers can be team members <mfg>cbaines: thanks, I'll read that :) <apteryx>mfg: non-committers can be part of teams yes <apteryx>to add a team, you modify etc/teams.scm and you open a PR <apteryx>or you discuss it on guix-devel to see if others would like to join first <mfg>apteryx: thanks, for the suggestions <bremner>err. now It seems to be building. Maybe it was as silly as being on the wrong branch <bremner>beginner mind sometimes means I don't know when to expect success. <bremner>guix system: error: /home/bremner/software/guix/gnu/packages/web.scm:6184:2: package `jq@1.8.2' has an invalid input: ("_" #<syntax-transformer oniguruma>) <user220>@coopi why not source etc/profile instead? <joostvb>bremner: at least the error messages are interesting.... (scnr) <graywolf>Does --keep-going not work together with -P or am I just holding `guix build' wrong? <ieure>graywolf, I think it works, maybe the rest of the packages you have to build can't be built because one of their inputs failed? <graywolf>Maybe? Though every time I re-run it, it at least downloads some additional substitutes, so it seems there is more work that *can* be done. Hm. <graywolf>Now that I think about it, it would be useful if -P had some way to exclude known-failing packages <jlicht>efraim: uvwasi also fails for me on i686-linux, yet the test seems to succeed when not running in the container. Is there some way to get a coredump from withint the guix build process? <jlicht>efraim: ah found it with good ol' objdump; seems the tests were only succeeding on x86_64 due to luck; relevant stuff was in a assert(..), which does not play nicely with our NDEBUG <untrusem>jlicht, your quickjs build system pr is super cool <jlicht>untrusem: thanks, I spent *quite* some time on getting the llhttp "replacement" in a workable state. Just happy it bore fruit <Elwood_Soup>Hi y'all! Looking for some help installing Guix on a RockPro64. I have Debian running on the SD card and I'm trying to run 'guix system init' to install it to the EMMC. Getting an error about an unbound variable even though I've added the appropriate module under use-service-modules. Any help would be appreciated. SCM and log to follow. <ieure>Elwood_Soup, Your config seems fine, (gnu services desktop) is where plasma-desktop-service-type is defined. What commit of Guix does `guix describe' show? I vaguely remember the KDE stuff being in a different module at one point, maybe you're on an older commit and it's not where you expect? <Elwood_Soup>For context, I'm assuming the problem is related to me running guix under sudo, but running it without sudo gave me an 'i/o file protection' error <Noisytoot>Elwood_Soup: can your user write to /mnt/emmc? <Elwood_Soup>Noisytoot: yes, /mnt/emmc is owned by my user with 777. It copies to /mnt/emmc for quite a while before it fails. I think it fails trying to install the bootloader.