IRC channel logs
2026-06-29.log
back to list of logs
<jayq>hi all! I'm watching a fresh foreign distro install doing its first guix pull, and am seeing some "error (ignored): program `newgidmap' failed with exit code 1" errors. It says ignored and this is a test machine so I'm not gonna stresss about it, but any idea whats up? <jayq>Oh, some SELinux denial related to kanidm. That'll be fun to debug... <PotentialUser-10>hello. i would like to add an executable to my PATH, specifically dotnet (used the dotnet installer script from ms) how would i achieve this for my home profile? <Useless_II> I believe there is already a dotnet package on guix, is there a reason you need the locally installed version? <PotentialUser-10>Useless_II i thought there wasnt a dotnet package on guix. i need to run some software that requires it. <Useless_II>when I guix search for it i'm able to find it, although it's possible it's on the non-free channel as I have that channel being used as well. Does `guix search dotnet` yield you any results? <PotentialUser-10>hmm. i still dont see it in the search results. should i add that channel to my home profile? <Useless_II>Yea you can add that channel and then pull to update everything. I can't remember my exact steps anymore I added it a while back. Alternatively if you can't find stuff you need on the non-free repo you can still add things to your path with an export command similar to how you would in other linux distros, or update your home configuration to add a <Useless_II>new path and put your binaries wherever it points to <PotentialUser-10> ;; `(("PATH" . "$HOME/.dotnet")))` but i know its not right since i got locked out of my user account <RavenJoad>PotentialUser-10: You got "locked out" because you messed with $PATH, I bet. You are just assigning $HOME/.dotnet to $PATH and discarding all the rest. You need to prepend/append instead using the standard $PATH delimiter. <PotentialUser-10>RavenJoad how do i append using the $PATH delimiter? i looked over the docs regardign home-environment-variables as a guide when i wrote that <RavenJoad>PotentialUser-10: The same way you would append in shell. `(("PATH" . "$PATH:$HOME/.dotnet")) is the naive solution. If you are using bash, you can be safer with its ${PATH:+:} expander. <PotentialUser-10>RavenJoad is there documentation for the PATH expander? otoh if i use home-environment-variables service do i need to extend it for the other solution? im using bash. <RavenJoad>Not in Guix's manual. The expansion is in Bash's info manual. To prepend, it is PATH="thing-to-prepend${PATH:+:$PATH}" <RavenJoad>You will need to prepend/append to $PATH regardless of you populate home-environment-variables. <RavenJoad>If you build the home config and look at the profile that gets output, the things you put in home-environment-variables essentially gets copied verbatim to the shell config file. <PotentialUser-10>RavenJoad oh ok. so something like this? `PATH="$HOME/.dotnet${PATH:+:$PATH}"` <RavenJoad>Yeah, that looks reasonable. Obviously test it in a shell before committing to it. <RavenJoad>Then you would do `(("PATH" . "$HOME/.dotnet${PATH:+:$PATH}")) in your home-environment. <PotentialUser-10>RavenJoad hmm. if i get an error saying that the target service (home-environment-variables-service-type) is used more than once, do i have to extend it? <jayq>I have a fresh foreign distro install, it seems like the daemon is working, and I can use guix as root. How do I "bootstrap" a Guix profile for a normal user account? Do I initially source root's /var/guix/profiles/per-user/root/current-guix on my user account? <sham1>Can you run `guix pull` on your user account <sham1>Like with just `guix` from your normal $PATH <jayq>I dont have guix in my normal path <jayq>I suppose thats the question <Rutherther>jayq: what login shell are you using? Did you relog to get the new env vars? <Rutherther>Or alternatively source /etc/profile, but that will activate only in the shell you use, not everywhere <jayq>I'm using fish, and I did not. I'm reading the profile scripts that guix-install.sh creates. They are sourcingfrom $HOME/.config/guix/current, but thats not gonna exist <jayq>I'm trying to keep the default login environment "clean" and not activate guix by default <jayq>i.e. I want the default login to be the pure foreign distro with no guix stuff <jayq>but anyway, I'm dissecting the guix-install.sh script and not seeing how the initial $HOME/.config/guix/current is created <sham1>$HOME/.config/guix/current is created with guix pull <sham1>(It's also the wrong place for that, grumble grumble, but that's not really relevant here) <jayq>I figured that guix pull would set that up, I'm currently doing the initial guix pull on my user account with root's current guix added to PATH <jayq>I've always found the ~/.config/guix/current path a bit weird too. I guess for us in XDG dir land, the correct place for all guix profile paths would be either $XDG_STATE_HOME or $XDG_DATA_HOME <jayq>running guix pull with root's current guix in path did indeed create the users ~/.config/guix/current which I can now jump to. I had to manually as root create /var/guix/profiles/per-user/jayq and chown which was a bit unexpected <futurile>Morning all - hope it's not too hot where ever you are! <sham1>Being at the office is surprisingly nice at this time of year, since this place has proper air conditioning <futurile>sham1: heh heh, maybe that will be on job adverts in future as a perk "free fruit, tea/coffee and you won't boil to death in your Victorian brick built flat with our modern aircon ... headphones for focused work not supplied" <csantosb>Heat is relative, trust a guy from The South, open your windows at night, you'll avoid the need air cond, good morning, by the way ! <csantosb>Speaking of windows and heating the planet, I've been playing with the idea of distributing topic specific Guix packages with help of podman, see codeberg.org/csantosb/eda-tools <identity>proper air circulation makes a huge difference. a stove is not that hot if you keep it open <bjc>i still have to manually delete /etc/resolv.conf and restart NetworkManager on every reboot. is this going to get fixed or reverted? <identity>bjc: that should have been a one-time problem, and was in my case <bjc>it is not for me, i do it every day now <bjc>possibly, probably even, because i have a tmpfs / <bjc>but this still indicates an ordering bug <noxi>is there a not-obvious reason why gcc-toolchain doesn't include the `cc` symlink? <noxi>especially since clang has `cc`, and gcc even has `cpp` and `c++` <noxi>oh yeah no cpp is the c pre-processor <noxi>c++ is definitely the same as g++ though <identity>apparently c++ is just a copy of g++, not a symbolic link <jresich>is there a way to mute users on codeberg? i'd like to mute the cuirass bot's notifications <czan>Hmm. You can block a user on its user page (behind the three-dot menu), but I don't know exactly what that does... <noxi>identity: so I wrote a small patch to symlink bin/cc to bin/gcc. since it touches make-gcc-toolchain and not the gcc packages, I think it might not even trigger any big rebuilds... at least guix build --dependents built nothing but gcc-toolchain <identity>nothing «depends» on gcc-toolchain, at least not explicitly, i think. i expect it would still be a world rebuilt <EndureAhead>Dear Guix Maintainers, I have sent emails to guix-maintainers@gnu.org about possible opportunities in areas I mentioned. is that email correct? <ekaitz>EndureAhead: apteryx and efraim are the maintainers I think <sneek>Welcome back ekaitz, you have 2 messages! <sneek>ekaitz, old says: if guile is using more CPU time than expected for a single-threaded application, this is because of: Finalizer threads. Signal dispatcher threads. GC threads. <sneek>ekaitz, old says: you can't get rid of the first two AFAIK, but you can restrict the GC threads like so: GC_NPROCS=1 <ekaitz>oh we have to do something about sneek giving us messages in the wrong room <identity>i wonder how old the «we should teach sneek about different channels» thing is. i keep seeing it popping up once in a while <gabber>csantosb: this is actually awesome! we at F-Si were glancing at such a goal for quite some time—but I guess you already heard that, right? <csantosb>Correct, this is a recurrent need within the community <gabber>when i joined F-Si they told me about this monolithic, all-including docker image from austria(i think) <csantosb>The work is not over: we need to test, make use of it, and document; I don't expect it all to work out of the box <gabber>unfortunately i am not very apt with hardware development, so apart from the software/guix/packaging side i can't give you all that much input <gabber>csantosb: i can help with documentation (and maybe even spreading the word) <gabber>liberating the toolchains is quite a big thing in this domain <csantosb>I'm afraid I won't; but this is the right moment to spread the word <csantosb>By the way, I didn't build the full image with all inside, too big; I think that fewer images makes it by now <csantosb>Still, the manifest is there, in case someone needs a bit more heating at home <gabber>i will try my best to spreading the word. at F-Si we're super excited about it <gabber>have you considered joining F-Si so we could maybe coordinate these efforts a bit more efficiently? or we could even have these manifests under `etc/electronics` in mainline guix and coordinate in team-electronics? WDYT? <gabber>untrusem: yeah, not sure we do that yet, but csantosb is way up for MVP in the electronics team (again) :P <csantosb>gabber, probably keeping these manifests in Guix would be nice to have, once they prove useful <gabber>maybe it's the other way around → they are (even more) useful when in mainline Guix <csantosb>Yeah, probably; I'll need to clean them up a bit before. <gabber>I'll happily help you with that. I figure you're open for PRs? <RavenJoad>I posted an email to the guix-devel mailing list yesterday and haven't heard anything back. I understand this may be a low-volume list, but I would have assumed an automated response from the system about receiving it. <identity>RavenJoad: if you did not post on GNU mailing lists before, it might take about a week to get through moderation <RavenJoad>untrusem: identity: Yeah, first mail there, probably. Ah, ok. Just double-checking. I would have expected a "your mail has been received and will be posted after moderators/admins read it over." Thanks! <hjolmir_the_peni>> RavenJoad: if you did not post on GNU mailing lists before, it might take about a week to get through moderation