| 22 Dec 2025 |
 emily | in practice things are usually either sufficiently wide fan-out that it doesn't really matter what you pick, or bottlenecked on few enough things that it doesn't really matter what you pick, so it's not a huge deal unless you have few build slots | 00:07:41 |
|  KFears (they/them) changed their display name from KFears (burnt out) to KFears (they/them). | 00:08:50 |
 whispers (it/fae) | huh fair, ty | 00:10:40 |
 raitobezarius | (untrusted) spare hardware still needs tending so it's up to the amount of infra resources available, we already have remote beefy builders for doing things, x86 CI is not bottlenecked in any way, Darwin is always the limiting factor | 04:23:52 |
| raitobezarius | i'd recommend joining the afnix zulip and the infra channel and looking if you can pick up some tasks so that the team and you can take the time to know each other | 04:24:47 |
| raitobezarius | many tasks doesn't require root@ perms as deployment is rarely a bottleneck | 04:25:04 |
 Sofie 🏳️⚧️ (she/her) | Is GitHub down? | 09:53:09 |
| Sofie 🏳️⚧️ (she/her) | oh, not anymore | 09:53:37 |
| Sofie 🏳️⚧️ (she/her) | for a second I got 504s | 09:53:42 |
 bandithedoge | nixpkgs back at it again? | 09:56:40 |
| Sofie 🏳️⚧️ (she/her) | yea | 10:43:34 |
|  suya changed their profile picture. | 12:18:05 |
| 23 Dec 2025 |
|  McBeth joined the room. | 01:56:54 |
| McBeth | It's been months since I've successfully built my os. I was/am still on 2.93.2 and it keeps failing on
perl5.40.0-Test2-Harness-1.000161 failed with exit code 1
I've been singularly unsuccessful googling solutions for this, and I've been aggressively pulling things out of my config without anything getting better. | 02:00:35 |
| McBeth | I'm using flakes for my config, and have nixos-unstable, lix, home-manager, and nixos-hardware (all this is on a framework gen 11 intel) | 02:05:37 |
| McBeth | * It's been months (July) since I've successfully built my os. I was/am still on 2.93.2 and it keeps failing on
perl5.40.0-Test2-Harness-1.000161 failed with exit code 1
I've been singularly unsuccessful googling solutions for this, and I've been aggressively pulling things out of my config without anything getting better. | 02:07:03 |
| raitobezarius | 2.93.2 had a known critical bug, do you have your configuration somewhere public? | 03:00:32 |
| raitobezarius | Can you provide more logs so we can see what we could offer? | 03:00:55 |
| McBeth | I can do that. I knew I wasn't providing enough info. I've never really learned how to get the logs, but I'll work on getting the configs uploaded | 03:11:21 |
| McBeth | https://git.sr.ht/~mcbeth/nixos | 03:26:34 |
 just1602 | Can you provide the error you get in your terminal when you do nixos-rebuild or whatever command you run to update your machine?
If you didn't run nix-collect-garbage you could boot into a previous generation with a previous lix version to update to the latest version? Otherwise I think there's a way to use a static build to rebuild your system, but raitobezarius is really the expert since he lead the fix when it appeared.
| 03:30:37 |
| McBeth | 
Download Screenshot from 2025-12-22 22-34-39.png | 03:35:28 |
| McBeth | I also have tried the same thing, but with a nix-shell -p lix, which gives me 2.91-3, and get the same error | 03:36:23 |
| McBeth | * I also have tried the same thing, but with a nix-shell -p lix, which gives me 2.91.3, and get the same error | 03:36:34 |
| just1602 | Here's the blog post to fix the issue with 2.93.2: https://lix.systems/blog/2025-06-27-lix-critical-bug/
According to this article, 2.93.2 shouldn't be affected. Are you able to do repair your store first and then see if it works? | 03:40:10 |
| just1602 | But also in this screenshot, it's nixccp that is failing to build. Are you using lix? | 03:41:10 |
| McBeth | nix --version says nix (Lix, like Nix) 2.93.2 | 14:11:08 |
 K900 | Are you sure this is even a Lix issue | 14:15:00 |
| K900 | Can you post the full build log | 14:15:10 |
| McBeth | No, I'm not sure this is a lix issue, one of the struggles is that it's insisting on building a couple thousand of packages, so these failures sometimes take quite a while to show up. I've been really struggling to figure out ways to search for my own solutions rather than bugging others (I was prideful since July).
Sorry.
I'm running the above blog suggestion with the static build of lix right now, I'll post the full logs (once it finishes, assuming it still fails to complete) | 14:41:19 |
