IRC channel logs
2025-07-07.log
back to list of logs
<postroutine>I hade searched ways to manage secrets in Guix System/Home. Before and after a reconfigure. But I didn't found a lot of info. How do you usually do it ? <dodoyada>I'm interested in learning a new programming language. Must be functional, preferably typed but not a must, not a lisp/scheme (I'm trying to challenge my ideas on scheme supremacy). What are the best languages in terms of guix packages that would qualify? <PotentialUser-88>Hiii, I've got an issue since I guix pull and upgrade, my containers wont restart, I get this error: <sneek>PotentialUser-88, you have 1 message! <sneek>PotentialUser-88, csantosb says: see 6.10 Specifying Channel Authorizations and 7.5 Invoking ‘guix git authenticate’ for .guix-authorizations <PotentialUser-88>Unable to create container: Unknown runtime specified /gnu/store/vd5qqhi9mrpihnjfkg55hd9r1q2wzc20-runc-1.1.14/sbin/runc <Kolev>What's the best way to do Rust development on Guix? <podiki>PotentialUser-88: rebuild the docker image/environment <podiki>that happens because it captures the full path to something when it is first run/created, which later is gone (guix doesn't know about this reference so doesn't keep it) <podiki>e.g. docker --build --force-recreate .... <PotentialUser-88>but I was using portainer, that basically setup all the rest of my containers, how do I do that ? <podiki>sorry, no idea what that is, but look for something similar i guess, a way to rebuild all the containers <cobra>i remember trying to run guix system on a pentium iii machine a bit ago and it didnt work because of the cpu isa level <cobra>has that been fixed , and if not is fixing it planned <civodul>cobra: hi! was a bug reported for it? <civodul>though overall, i686 support is limited <efraim>I don't think we're as careful as debian about sticking to the ISA when it comes to SSE or other things, but I'll also point out that 2GB is about the lower bounds of what you'd want for RAM on the machine if you're running Guix System anyway <tazjin>dodoyada: I don't know about their guix support, but non-lispy functional languages worth learning are erlang (or elixir, based on which syntax you prefer) & haskell (or ocaml, if you want to not go all-in on the purity aspect) <tazjin>both of these will teach you new concepts that you won't as easily come across in Lisps <cobra>god forbid women want extremely esoteric guix machines smh <efraim>you're welcome to continue my work on 32-bit powerpc :) Guix works but I haven't tested anything related to the bootloader <jakef>hi guix, i'm getting a hash mismatch between guix download and during guix build <jakef>reproduced on 2 different machines <gabber>jakef: are you trying to craft a package definition for this itksnap repository? <gabber>or what are you trying to do in the end, exactly? <jakef>i might update itk-snap it if I can, yeah <jakef>thought i'd get further than updating the commit and hash though <jakef>ooo maybe its cause of git submodules <gabber>i usually just update the package definition, try to build (which fails due to the new hash) and then update the hash as indicated by guix' build process <gabber>i am not sure if there is a fool-proof way to get the correct hash other than trial-and-error <jakef>interesting. guix download is almost always correct for me <jakef>i get the same hash as guix build when i clone it, checkout the commit, and run 'guix hash --serializer=nar -x itksnap' <jakef>i wonder what i'm missing with guix download <jakef>its gotta be the submodules, surely <civodul>futurile: how many people have replied so far? <apteryx>is shepherd 1.0.5 the most recent release? <apteryx>sneek: later tell civodul it looks like shepherd 1.0.5 still has some memory leak issue; Shepherd was using > 700 MiB memory on a VPS of mine. <yelninei>hi, could I ask for some team-hurd labels on some of my issues. I dont see an option to do this myself <noe>you can get the option if you join a team <yelninei>noe: i am (since a couple of days ago) but i think it is not synced to codeberg yet <yelninei>yeah that page just returns the codeberg 404 <noe>sneek, later ask civodul if he could run the etc/teams.scm sync-codeberg script when he has time <yelninei>oh its manual that explains everything. I dont know why I thought this would happen automatically <noe>I don’t think it requires human intervention though, so it could probably work on a loop <yelninei> human intervention in the sense of someone with admin privileges in the org i guess <ieure>Anyone have suggestions for debugging why `guix system reconfigure' is segfaulting? Ran it under strace, didn't see anything obvious. <noe>ieure, gdb with the guile extension then? <ieure>noe, Been a minute since I've used gdb, and have never had to use it for non-C stuff. It refuses to run `guix', because it's a script file with guile in the shebang. How do I even get this stuff running under gdb? <noe>hehehe its quite annoying <noe>and I do not remember <noe>easier option: get a core dump and load it in gdb with the guile binary that was used to run guix <ieure>It segfaulted while printing a backtrace. <ieure>Coredump isn't very helpful, the last thing on the stack is: #0 0x00007f36d2e0e377 in ?? () from /gnu/store/9jcmmhrmp66wa3zl4rfi9fl72v4jhhxz-guile-3.0.9/lib/libguile-3.0.so.1 <ieure>And the previous is: #1 0x00007f36d2e1bd85 in scm_call_n () from /gnu/store/9jcmmhrmp66wa3zl4rfi9fl72v4jhhxz-guile-3.0.9/lib/libguile-3.0.so.1 <noe>Oof, segfault on backtrace <noe>frame 9 seems interesting <ieure>Yeah, that seems to be the thing that triggered the segfault. But... this shouldn't segfault. <av>guys is ci.guix.gnu.org down :( <ieure>av, All the Guix infra is flapping down constantly. <av>either way im NOT going to compile packages locally <av>it hurts the poor planet <av>i got lucky because i worked