IRC channel logs
2025-06-14.log
back to list of logs
<untrusem>so some things happed while reconfiguring the the system and it broke <untrusem>so I switched to previous generation, _guix :)__ but whenever I try to switch generation to the previous one I can't it is giving `guix system: error: unrecognized boot parameters at '/var/guix/profiles/system-8-link/parameters'` <meaty>untrusem: have you tried switching to _other_ other generations? <untrusem>guix system: error: unrecognized boot parameters at '/var/guix/profiles/system/parameters' <meaty>wait, are you switching generations using the menu in grub? <untrusem>I reconfigured, system bricked, I booted into the older generation then <untrusem>and the above error are in that booted generation <meaty>what filesystem were you using? was it one of the ones listed in the error? <ruther>untrusem: what suggestions don't work exactly? <ruther>I see I made a mistake in the suggestions, should be -p /var/guix/profiles/system, system is missing there <untrusem>it worked, you should add sudo too in the message <ruther>no, I won't add sudo to the message <untrusem>so while reconfiguring now, grub-cfg build failed <ruther>untrusem: seems more files are corrupted, yeah, that usually happens that it's not just one file <ruther>untrusem: you can run the store verification with repair and hope that it's just substitutable paths that are wrong <ruther>untrusem: yes, but also with contents, not just repair <untrusem>ok I have that in my shell history, not my first time :) <untrusem>took around 40 min, damn, now reconfiguring the system again <untrusem>guix system: error: error parsing derivation `/gnu/store/a5z9v4qj7m1apwapy3gp4s29gb0c2pb5-module-import-compiled.drv': expected string `Derive([' <identity>untrusem: `guix gc --delete corrupted.drv' might help, not sure <ruther>untrusem: you need to read the output of the verify, not just ignore it. It contains information about what could not have been fixed, and you need to fix that in other ways <untrusem>I switched generation again thinking that the current generation might be curropted too, so doing the steps again <Kabouik>Is there a way to use Nix with a guix shell? Like I would want to try rix, which is a Nix way to do reproducible research using Nix (I don't know if I would use it myself as I have Guix already, but I may need to test it for others), and I don't necessarily want to clutter my system with the Nix store, so a guix shell would be nice, but I'm afraid Nix being used from the shell would still need to write to /nix/store and couldn't write to a <Kabouik>subdirectory of the guix shell hashed path. <identity`>Kabouik: you probably need to write to /nix/store, unfortunately <Kabouik>Thanks! I wish there was a way to change the prefix easily and put everything in a /tmp/ parent dir for testing purposes <Kabouik>I'm puzzled. I updated my config.scm and now fail to system reconfigure but I can't see the relationship between my changes and the error: https://0x0.st/8EC5.txt <Kabouik>I just didn't catch it in the diff, copy/paste error. <ikitori>I am considering switching to Guix System on my daily driver without having great proficiency in Scheme and the goal to learn it in progress <ieure>ikitori, YMMV, but I personally wouldn't reinstall daily driver hardware to *any* distro I had no experience with. <ieure>ikitori, If you have limited Scheme, but are comfortable with Guix as a foreign package manager, that would change my thinking a bit. <ikitori>ieure, my second computer has already been using Guix System and it works. I would start from there <ikitori>I still have no idea how to write a service to configure tools I use if they aren't already there. Do you believe this would be to big of an obstacle? <ieure>ikitori, That's a very subjective question. I personally found writing simple Guix packages very easy, and services a little bit harder -- but I'm was proficient in multiple non-Scheme Lisps. <identity>ikitori: i used Guix for some time before defining any packages/services with no problem, so again, YMMV <luca>While I like guix, there are a dozen distros which are easier to install and make packages for. But declarative system management is really where guix shines IMO <identity>i also would not say that doing any of that required much more than basic scheme and guile knowliedge that you could pick up on the way <ieure>Packaging... it depends. Having packaged for both Debian and Guix, Guix is much, much easier most of the time. <ieure>But if you want to package stuff written in a language that has a bajillion dependencies and uses lockfiles (Basically: NodeJS/Rust/Go), stuff becomes very annoying very quickly. <luca>Yeah debian is a bit wack and I never understood it. But arch/void/alpine/chimera are more comperable (and easier especially without lisp knowledge) <ieure>luca, Yeah. Never used any of those because they didn't exist when I switched to Debian. <civodul>PSA: if you’re a Guix Foundation member, consider joining the general assembly now! <ieure>tusharhero, The patch was never pushed. <ieure>tusharhero, It looks like some changes were requested and the author never followed up. <tusharhero>Should I create an issue about it on the codeberg repo? <ieure>tusharhero, If you like, but, if you want it actually done, you'll want to do it yourself, using the abandoned patch as a starting point. <ieure>tusharhero, Guix is volunteer-driven and most work is of the scratch-my-own-itch kind. Since it's been three years and nobody has picked up that patch or opened new ones around that work, I think not many people have the itch. <ieure>So -- if you want to contribute patches, those will likely be accepted. If you're asking someone else to do the work, you will likely be waiting a good while. <ieure>tusharhero, I'd recommend replacing the `define-record-type' with `define-configuration' -- that's what new stuff should be using. <ieure>tusharhero, You're welcome to put up a WIP PR and add the help-needed tag if you get stuck. <pastor>Hello, does anyone have python-grpcio@1.73.0? I need it for another package I'm doing but I'm struggling updating it. <ieure>pastor, Check the python-team branch. <pastor>ieure: unfortunately its still on v1.47.0 <ieure>pastor, What problems are you having updating it? <pastor>The thing is that I tried to debugg what looks like the error, but that `a.o` file is properly compiling. So the GCC error is probably from something elese, but I don't know what. So I'm stucked <ieure>pastor, Going to hazard it might be related to the "creating None/tmp/guix-build-python-grpcio-1.73.0.drv-0" lines in the output, which mean some variable the build process expects is unset. <pastor>I've also tried to modify the sources to print some more info, but I could not locate the error. <ieure>pastor, See the Guix manual, 9.1.4 Debugging Build Failures. <pastor>Yeah. It looks like a string is not initialized. But checking the output with `guix build ... -K' the file is compiled in that `None/...' folder. <ieure>But tl;tr build with -K to preserve the build env, then `guix shell -D python-grpcio' to make the inputs available. Then poke around the source tree / run the build manually to debug. <ieure>pastor, Right -- but it could very well be causing other issues. <pastor>Alright. I will try to run the build manually. 