Nix on macOS | 1184 Members | |
| “There are still many issues with the Darwin platform but most of it is quite usable.” — http://yves.gnu-darwin.org | 193 Servers |
| Sender | Message | Time |
|---|---|---|
| 22 Apr 2026 | ||
idk if i did an oopsie but i have 2 users on my machine and sometimes i can't darwin-rebuild switch from one of them (something something "need permissions to update applications" something something "if you didn't get a notification go to settings -> privacy & security -> ...")like, i dont get the notification, and the system settings seem fine... ...but then i switched to the other user and... oh! a notification! ...what?? and i can darwin-rebuild switch from that other user....is this a known/common issue? | 09:48:49 | |
| it only happens sometimes for some reason | 09:48:59 | |
things that might be relevant idk:
| 09:53:04 | |
things that might be relevant idk:
| 09:53:19 | |
| 11:50:30 | ||
| Hammerspoon compiled through swbuild 🎉 {"id":92,"kind":"targetComplete"} {"kind":"buildCompleted","result":"ok"} Now there's so much to patch / upstream / whatever. I'll open a tracking issue for that, because I'm still trying to figure out what is still alive and what I need to fork (sigtool is unknown for example) | 23:22:01 | |
Download Screenshot 2026-04-23 at 9.30.02 am.png | 23:30:12 | |
| 23 Apr 2026 | ||
| Tracking hammerspoon, but actually also the overall xcode building https://github.com/NixOS/nixpkgs/issues/512622 | 02:09:27 | |
| sigtool needs replacing with rcodesign | 02:12:15 | |
| no point maintaining that moribund codebase | 02:12:20 | |
| wow, rcodesign has some serious dependency explosion, I don't wanna know why it's compiling aws-sdk-sso 😱 | 02:23:37 | |
| also the CLI options are incompatible with codesign... I'll have to check if patching swift-build, or a wrapper would be more reasonable. | 02:24:57 | |
it needs a codesign(1)-compatible CLI upstream, but the underlying library implements everything required | 02:59:06 | |
| if sigtool has any value left and there are people willing to continue developing it, I think we should transfer it to nix-community or similar | 03:09:41 | |
| I asked, let's see https://github.com/indygreg/apple-platform-rs/issues/300 | 03:35:15 | |
| https://github.com/indygreg/apple-platform-rs/issues/24 | 11:16:54 | |
| 🤦 I actually looked through the open issues, missed it. Thanks for the link | 11:18:30 | |
| PSA: Don’t let your disk fill up, or you won’t be able to delete any files. Whoops. | 12:56:17 | |
| I left a build going overnight while I was away. I came back to 91 MiB free space on my disk. I had to delete the store to free up space. I’m working to get things back online now. | 12:56:39 | |
| Don't get close to full either... the latency gets absurd in the high 90%s 😢 | 14:22:52 | |
| Does anyone know how to set up a Linux builder with Determinate Nix? I wanted to try it, but maybe it is hidden behind some feature toggle or I'm clueless. With nix-darwin I can set nix.linux-builder.enable = true, does determinate have its own module I need to include? | 14:39:21 | |
| afaiu the linux builder for determinate is experimental and invite-only,at least last I checked | 14:41:33 | |
| you can email them for access: https://docs.determinate.systems/troubleshooting/native-linux-builder/ | 14:42:13 | |
| Thanks, I should have read the fine print. I will try the email route. | 16:01:54 | |
Okay, I’m back. Deleting the store and doing some cleanup freed up ~400 GiB of space. I should hopefully be good for a while. Took the opportunity to update to Lix 2.95.1. Yay for being able to set log-format in nix.conf. | 16:32:15 | |
| RandyEckenrode: Do you mean Nix won't be able to GC? Or does APFS suffer from the issues Btrfs used to run into? | 17:58:57 | |
| APFS needs free space to delete files in a volume. I had to make space by deleting a volume in the same container. | 18:32:01 | |
| I think that’s the same as btrfs and ZFS. | 18:32:31 | |
| Btrfs used to have such a problem but reserves some space to always be able to delete something now I think. | 19:54:18 | |
| Has anyone else seen a Python package die due to code signing? Termination Reason: Namespace CODESIGNING, Code 2, Invalid Page | 23:16:24 | |