| 20 Nov 2025 |
Randy Eckenrode | I'm tracking HEAD in my work. There’s still work being done. | 14:16:39 |
Randy Eckenrode | According to Alyssa, feature parity with MoltenVK will happen, which means we may be able to use it by default in the future. | 14:17:30 |
Randy Eckenrode | Timing-wise, it works out really well for 26.11. | 14:17:54 |
Randy Eckenrode | KosmicKrisp requires at least macOS 15 and doesn’t support GPUs other than Apple Silicon. We’ll be bumping the minimum to 15.0 and dropping Intel support at that time. | 14:18:52 |
Randy Eckenrode | There won’t be a need for elaborate mechanisms to seap the GPU driver. | 14:19:18 |
Randy Eckenrode | * | 14:19:26 |
Randy Eckenrode | * | 14:19:38 |
Randy Eckenrode | RIP Wine on Darwin though. | 14:19:46 |
Randy Eckenrode | Apparently FEX doesn’t support 16k pages, and upstream doesn’t seem interested in supporting it. | 14:20:19 |
Randy Eckenrode | If Asahi maintains patches, we may be able to use those, but I don’t know. | 14:20:55 |
Alyssa Ross | Asahi runs FEX in a 4K page VM | 14:22:34 |
Randy Eckenrode | I thought FEX was the VM-less solution. | 14:23:00 |
Alyssa Ross | No, FEX is the x86_64→aarch64 part | 14:23:21 |
Randy Eckenrode | Or is it just less of one compared to the previous implementation? | 14:23:24 |
Alyssa Ross | the VM is the 16K→4K part | 14:23:28 |
Randy Eckenrode | Ah. I guess we need to hope CodeWeavers does the work. | 14:23:55 |
Spore | https://github.com/AndreRH/hangover/issues/97#issuecomment-2991121847
What does this mean tho | 14:24:05 |
Randy Eckenrode | Sounds like FEX with Wine’s large page support mostly works, but there will always be some limitations. I don’t know what that means for Darwin. This is a Linux repo. | 14:30:02 |
Randy Eckenrode | I assume https://github.com/FEX-Emu/FEX/issues/5046 is about native support (replacing Rosetta 2). | 14:32:00 |
| Yevhen Zhyhalo joined the room. | 16:08:23 |
validitymaiden | I'm noticing a lot of references I'm reading using system = arch where arch is some platform and machine architecture. However, in my nix-darwin flake system is an attribute set with, at minimum, the attributes configurationRevision, stateVersion, and primaryUser. For context, I am coming to this through my attempt at adding an additional nixpkgs input. Does nix-darwin require a different object named system than nixos flake expressions? | 22:59:09 |
validitymaiden | I suppose I should have prefaced this with asking whether this channel is an appropriate place to as such basic nix questions. Feel free to ignore / direct me to a more appropriate place. To note, I am so grateful for all the work y'all are doing. It's amazing and really appreciated. | 23:02:27 |
samasaur | those are actually totally separate things. the system in system = "aarch64-darwin" (or whatever other arch) is an argument to the nix-darwin.lib.darwinSystem function that takes an architecture and a list of modules and produces a nix-darwin system configuration. its analogous form is the system argument to the nixpkgs.lib.nixosSystem function that takes an architecture and a list of modules and produces a NixOS system configuration.
the system with configurationRevision, stateVersion, and primaryUser (among others) is a namespace of nix-darwin options that you can set which will affect the generated configuration. some of those fields (such as configurationRevision) are the same as the corresponding NixOS fields, while others (such as primaryUser) are unique to nix-darwin
| 23:14:10 |
samasaur | so the short answer is "no, in your flake.nix both the nixpkgs.lib.nixosSystem and nix-darwin.lib.darwinSystem functions take the same type (a string representing an architecture) for the system argument" | 23:15:48 |
samasaur | (i'm saying architecture above to avoid saying "system" even more times to avoid confusion, but given that those strings have kernel information as well, they don't truly represent only an architecture) | 23:17:08 |
John Wiegley | Has anyone seen this sort of error before? It happens every time I try to darwin-rebuild switch now, but only on one of my machines. I've wiped ~/.cache/nix, rebooted the machine, repaired the store, etc., with no effect:
… while fetching the input 'github:nixos/nixpkgs/a8d610af3f1a5fb71e23e08434d8d61a466fc942?narHash=sha256-v5afmLjn/uyD9EQuPBn7nZuaZVV9r%2BJerayK/4wvdWA%3D'
error: cannot enqueue a work item while the thread pool is shutting down
| 23:37:33 |
John Wiegley | aha, https://brainxx.site/blog/fixing-too-many-open-files gives the answer: need to raise my file limit, although the error message really doesn't indicate that | 23:41:36 |
| 21 Nov 2025 |
debtquity | anybody else seeing this while updating to latest nixpkgs?
system-applications> building '/nix/store/qb1b66gq4fla4zgwi1k3fari06a84afs-system-applications.drv'
system-applications> building '/nix/store/xrhfxwxhmqxg1j0yblsp8zdrgcbbij58-system-applications.drv'
system-path> building '/nix/store/dm8cdyp905l4v4nyxl95x587fbw8kw9h-system-path.drv'
system-applications> created 5 symlinks in user environment
system-applications> pkgs.buildEnv error: Can't use string ("/Applications") as an ARRAY ref while "strict refs" in use at /nix/store/xk1hzr5rxgwmqm3lxspr2clayv1a4m7n-builder.pl line 18.
error: builder for '/nix/store/xrhfxwxhmqxg1j0yblsp8zdrgcbbij58-system-applications.drv' failed with exit code 255;
| 00:52:02 |
samasaur | you're probably using buildEnv in your own config | 00:52:28 |
debtquity | hmm | 00:53:05 |