| 26 Jul 2025 |
 raitobezarius | but I think the Lix team has almost no available Darwin expertise these days | 21:08:55 |
 emily | oh no Docker | 21:09:05 |
| raitobezarius | In reply to @emilazy:matrix.org
oh no Docker https://github.com/RaitoBezarius/bencher/blob/main/default.nix | 21:09:19 |
| raitobezarius | it's almost done | 21:09:20 |
| raitobezarius | just some pnpm & wasm garbage | 21:09:24 |
| raitobezarius | but i cannot fix release blockers and do that at the same time [and the 26 bazillion of things] | 21:09:40 |
| emily | the Emily team's Darwin expertise is also oversubscribed 😔 | 21:09:41 |
| emily | much as I would like to put work in | 21:09:46 |
| 27 Jul 2025 |
 aloisw | In reply to @raitobezarius:matrix.org
realistically, how often CA certificates changes mid-builds? I think we specifically started copying it to prevent this from causing trouble? | 05:00:45 |
|  Puna joined the room. | 06:59:20 |
 gilice | Download console.patch | 10:10:18 |
| gilice | hi, random guy chiming in here, I got the console output of your default.nix to build.
here's a patch: | 10:10:22 |
| Puna | Hi!
I see there's a host_cpu variable in meson.build where some fixups are being done to turn Meson's cpu_family() results to values that Nixpkgs expects for system parsing. Is that variable actually wired up to anything invisibly, or is it just completely unused right now?
I tried to add more fixups to it for POWER CPUs, but the system string stays wrong. Only if i change the host_system below it to actually use it do I get a correct system name printed. | 11:52:13 |
 Qyriad | It determines the default builtins.currentSystem value Lix is compiled with, I believe | 11:53:17 |
| Puna | I assume it should, but host_system is what's being used for that, and that just used cpu_family() | 11:54:20 |
| Qyriad | Oh I see what you mean now | 11:54:40 |
| Qyriad | that's a good question then, I'm not suredon' | 11:54:51 |
| Qyriad | * that's a good question then, I'm not sure | 11:54:56 |
| Puna | i think I submitted a theoretical fix for the POWER names? not super familiar with the gerrit workflow yet.
if host_cpu is supposed to be used there, should i make that a separate changelist thingy? | 12:33:39 |
|  kookie joined the room. | 13:40:00 |
| raitobezarius | In reply to @aloisw:julia0815.de
I think we specifically started copying it to prevent this from causing trouble? do you remember which commit / which thing introduced that? | 14:27:51 |
| raitobezarius | moved back to the non optimized version in https://gerrit.lix.systems/c/lix/+/3765/4?tab=comments | 14:27:56 |
| raitobezarius | and added a CL for the optimization | 14:28:00 |
| raitobezarius | with a FIXME for defending against UDS attacks | 14:28:04 |
| aloisw | https://git.lix.systems/lix-project/lix/commit/cf756fdf3c1a804af726703a12ed2990ad6c2639 | 14:30:02 |
| aloisw | According to the commit message here the motivation was avoiding broken symlinks, but the linked commit doing the same for resolv.conf also cites changing file. | 14:30:54 |
| emily | I feel like the store thing would achieve a comparable optimization across platforms while solving any UDS / file changing / etc. worries (but I should stop saying this because I suspect there is complexity to arranging the store copy that i'm just missing :) ) | 15:32:07 |
| emily | copying all the time sounds great to me if Linux has to do it too though :P | 15:32:24 |
| emily | how do you select a range of lines to comment on in Gerrit? | 15:58:20 |
| emily | I feel like I forget and have to remember how every time | 15:58:28 |
