| 18 Apr 2026 |
 mdaniels5757 | https://github.com/NixOS/nixpkgs/commit/f1bcb61731224bd8440510fc620d3c51f3e51c85 is the problem I think | 20:13:45 |
| mdaniels5757 | Fixing | 20:15:56 |
| mdaniels5757 | https://github.com/NixOS/nixpkgs/pull/511225 | 20:23:52 |
| mdaniels5757 | Reviewed and merged, if someone wants to kick off another eval of NixOS unstable. | 20:32:06 |
| 19 Apr 2026 |
 tfc | oh my god i think i force-pushed to staging-nixos, can someone please check and help me revert if i am right? | 17:11:31 |
| tfc | that was not my intention | 17:12:02 |
| tfc | oh it was also not my intention to post it here and wanted to psot in staging instead. sorry for the noise. | 17:12:19 |
 hexa | is that even possible? | 17:16:01 |
| tfc | i think it should not. continuing the discussion in staging channel | 17:16:36 |
| hexa | emily, Alyssa Ross? | 17:16:50 |
| 20 Apr 2026 |
|  picnoir changed their display name from Picnoir to picnoir. | 10:05:32 |
|  PhiliPdB joined the room. | 20:57:59 |
| 21 Apr 2026 |
|  gigacode joined the room. | 01:37:18 |
 dramforever | how far are we from flipping on ca-derivations for nixpkgs and {hydra,cache}.nixos.org? i'm looking for some estimate on the level of like "in 2026" "probably before 2028" "at least five years" | 02:32:15 |
 K900 | Possibly never | 04:44:25 |
| K900 | There are fundamental problems with ca-drvs that have yet to be solved | 04:45:02 |
| dramforever | "nowhere near" is fine, thanks for the info | 04:46:09 |
| K900 | The very short version is that ca-drvs relying on rewriting all references at build time basically means every single thing that embeds a reference in a non-trivial way needs to somehow be special cased AND rewritten without breaking things | 04:48:05 |
| K900 | With refscan it's at least fairly likely that even if you miss a spot, you'll find the same dependency in another location | 04:48:39 |
| K900 | With ca-drvs, the failure mode of missing a spot is "fire" | 04:48:52 |
| K900 | So like half of Qt immediately explodes on ca-drvs because QString is UTF-16 | 04:51:39 |
| K900 | So the rewrite pass completely misses like every other reference | 04:51:52 |
| dramforever | right, the thing i was wondering is if these things have been significantly worked on since i haven't heard much, which could be just me not listening to the right places | 04:54:43 |
| dramforever | but it sounds like it's more of a "no these are still problems" situation | 04:54:59 |
| dramforever | * but it sounds like it's more of a "no these are still very much problems" situation | 04:55:05 |
| K900 | They haven't no | 04:58:47 |
| dramforever | thanks | 04:59:03 |
 mynacol | I am the author of a partial rewrite of the deno package. I cannot reproduce the build failure on x86_64-linux. Is the correct approach to try a rebuild? | 14:54:32 |
| mynacol | * I am the author of a partial rewrite of the deno package. I cannot reproduce the build failure on x86_64-linux (the other systems built fine). Is the correct approach to try a rebuild? | 14:55:02 |
| hexa | uh, I built that yesterday on my desktop | 14:57:08 |
