IRC channel logs
2026-08-16.log
back to list of logs
<perryprog>oh, well doing guix pull --commit=(that commit) doesn't work? "guix pull: error: Git error: object not found - no match for id (b5e720b1b7f63b95f9f949a0d9e548aa4ea827cb)" <nckx>perryprog: Did you use --url to point to that fork (at your entirely own risk, including that it is indeed not a cherry-pick)? <perryprog>for some reason I thought that was merged -.- <nckx>Well, I didn't verify that the commit isn't also in the upstream repo somehow. <perryprog>I don't believe it is given the issue it referenced is still open <nckx>Ah, I meant in a branch. <perryprog>but regardless, I still feel like there... should be a way for me to unstuck this? I can't guix edit the problematic package, and I'm not sure what package is ultimately responsible for depending on it <nckx>I didn't follow your top-level quest TBH, I just arrived. <ieure>perryprog, `guix edit' is more of a development tool, it doesn't edit the package definition that Guix actually uses. <perryprog>nckx: it's "install guix on aarch64" and that's apparently harder than it sounds <ieure>perryprog, Ah, yeah, this is taking a while to merge because it'll cause a bunch of rebuilds. <ieure>Stuff that triggers >300 package rebuilds gets put on a branch so CI can rebuild all those and substitutes are available when the branch merges. <ieure>Otherwise everyone has to recompile a bunch of stuff. <perryprog>Fair enough. So there isn't any guixy way to modify a package's definition just for myself? I suppose a guix git checkout is one way but that seems overkill for just getting guix to uh... run <sham1>Well you can technically make yourself a module that you can then use with -L <sham1>To add it to the load path and then import and such <perryprog>alternatively, how can I figure out what module is responsible for requiring it? I'd love to just be able to reconfigure even if it's not a graphical environment <perryprog>or a way to run reconfigure with an equivalent to --without-tests 🤔 <fishwaffle>hey i just wrote a guix usb and its failing to install <fishwaffle>guix system: error build of '/gnu/store/gm14mklg7... <fishwaffle>command guix system init --fallback /mnt/etc/config.scm /mnt exited with value 1 <fishwaffle>whats weird is im reinstalling whats currently a working guix install <ieure>perryprog, I don't believe there's a way to find a path from a system configuration to a specific package. Being a colorspace management thing, it's likely some desktop environment stuff is causing the issue. I'd remove any DE/WM/GUI stuff from my system config and see if that helps. <ieure>perryprog, You don't want to build using a no-tests transform. Run tests or not is not a global switch, it's part of every individual package definition. Changing that value changes the package derivation, which means you have to compile everything from the ground up rather than using substitutes. <ieure>fishwaffle, What install media? What is failing to build? <fishwaffle>im using a usb drive with current guix x64 installer dd'ed to it <fishwaffle>this is on a thinkpad t580 that currently runs guix <fishwaffle>not actually sure whats failing to build other than python it said <fishwaffle>can i post a picture of my screen is that something i can do <perryprog>ieure: Removing xorg from the service module list doesn't help, and I'm running into complaints from guix if I try to remove desktop from the services. (Like missing udev) <perryprog>Welp. I went and did guix pull for the unreleased commit that fixes it, and skcms now builds... but now mutter is the issue with its tests also failing <edrx>guix package: error: profile '/var/guix/profiles/per-user/edrx/guix-profile' does not exist <edrx>(I just deleted the old install and reinstalled everything from zero) <edrx>apparently root has a profile but edrx doesn't have a profile yet - or looks so <ieure>edrx, You probably need to delete your $HOME/.guix-profile <edrx>ieure: I don't have a ~/.guix-profile <edrx>I deleted my old installation and /usr/local/bin/guix and the installer recreated /usr/local/bin/guix <spiderbit>Hi, I see that zram is supported via a service, but I don't find dokumentation about zswap and it's not activated by default theoretically it's a grub option or can be activated by that through boot. <ieure>spiderbit, You can set the zswap.enabled=1 kernel argument to get zswap. <perryprog>Why does guix X reconfigure need to spend time for "looking for substitutes" when I've just changed something like a minor setting? <perryprog>(Or more specifically, what network stuff is it doing at all?) <ieure>perryprog, It's looking for substitutes for the derivation of the operating-system itself. If you're making a trivial change that doesn't pull in new software, you can `sudo guix system reconfigure --no-substitutes' <ieure>At least -- I believe this is what it's doing. I don't know for sure. <untrusem>perryprog: how is your installation journey going on? <perryprog>I managed to trim down the global config to be entirely gui-less and that reconfigured just fine, so that's what I've been playing around in <perryprog>I will admit I find it a little disappointed that aarch64 is this funky right now (I would've imagined CI for "do the live CD steps" would've alerted things to this?), but I certainly can't blame anyone for that <untrusem>perryprog: you could try using time-machine to use crypto-branch I think <perryprog>I mean, I think I effectively was using the branch with guix pull --commit, no? <perryprog>yeah, it was pulling in gnome-console for reasons I couldn't figure out. Presumably %desktop-services or xorg. <perryprog>I would've figured it'd grab something much more lightweight if it needed a terminal that badly <untrusem>yeah you should use %dekstop-service for console use <perryprog>I mean I would've liked desktop stuff, but I didn't want it /that/ badly. Besides, the virtualization method I'm using only has 2d gpu acceleration so DE's tend to be rather laggy <perryprog>Gotta sleep, but thanks all for your help. (Positive outcomes or not!) Y'all rule <untrusem>is there used to be an option when there is a manifest.scm present in the directory, guix shell -- <cmd> will used it without specifying? 
