| 23 Apr 2026 |
 viraptor | wow, rcodesign has some serious dependency explosion, I don't wanna know why it's compiling aws-sdk-sso 😱 | 02:23:37 |
| viraptor | 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 |
 emily | it needs a codesign(1)-compatible CLI upstream, but the underlying library implements everything required | 02:59:06 |
 lorne | 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 |
| viraptor | I asked, let's see https://github.com/indygreg/apple-platform-rs/issues/300 | 03:35:15 |
| emily | https://github.com/indygreg/apple-platform-rs/issues/24 | 11:16:54 |
| viraptor | 🤦 I actually looked through the open issues, missed it. Thanks for the link | 11:18:30 |
 Randy Eckenrode | PSA: Don’t let your disk fill up, or you won’t be able to delete any files. Whoops. | 12:56:17 |
| Randy Eckenrode | 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 |
| viraptor | Don't get close to full either... the latency gets absurd in the high 90%s 😢 | 14:22:52 |
 jonhermansen | 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 |
 insipx | afaiu the linux builder for determinate is experimental and invite-only,at least last I checked | 14:41:33 |
| insipx | you can email them for access: https://docs.determinate.systems/troubleshooting/native-linux-builder/ | 14:42:13 |
| jonhermansen | Thanks, I should have read the fine print. I will try the email route. | 16:01:54 |
| Randy Eckenrode | 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 |
 toonn | 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 |
| Randy Eckenrode | 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 |
| Randy Eckenrode | I think that’s the same as btrfs and ZFS. | 18:32:31 |
| toonn | Btrfs used to have such a problem but reserves some space to always be able to delete something now I think. | 19:54:18 |
 Sarah Clark | Has anyone else seen a Python package die due to code signing? python3Packages.av crashes in pythonImportsCheckPhase (Killed: 9) and console shows `Exception Type: EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid))
Exception Subtype: UNKNOWN_0x32 at 0x00000001030973a0
Exception Codes: 0x0000000000000032, 0x00000001030973a0
Termination Reason: Namespace CODESIGNING, Code 2, Invalid Page
`
| 23:16:24 |
| Randy Eckenrode | Does it build a native extension? If so, I guess that could end up with a bad signature. | 23:17:19 |
| Sarah Clark | It's definitely using Cython | 23:19:06 |
| Randy Eckenrode | Is this on staging or master? | 23:20:19 |
| Sarah Clark | master | 23:20:27 |
| Randy Eckenrode | Staging got linker upgrade. (though I doubt it will help.) | 23:20:51 |
| Sarah Clark | I had no luck bisecting it -- ran into xxHash being missing (looks like one of the backport PRs did that) | 23:22:23 |
| 24 Apr 2026 |
| viraptor | Since I'm planning to fork xcbuild to include the bits needed for swift-build, I wanted to ask about the fate of tools in xcbuild conflicting with better implementations. Specifically xcbuild right now ships with buggy actool and not-quite-compatible PlistBuddy/plutil. I've got those ready in separate packages - actool and re-plistbuddy respectively. I could:
- leave the broken versions in place (confusing)
- remove those from xcbuild
- include my reimplementations in xcbuild automatically
I'm leaning towards option 2 and let projects include specific tools as needed, but could be convinced otherwise. Do people have strong opinions here?
| 01:09:56 |
| viraptor | * Since I'm planning to fork xcbuild to include the bits needed for swift-build, I wanted to ask about the fate of tools in xcbuild conflicting with better implementations. Specifically xcbuild right now ships with buggy actool and not-quite-compatible PlistBuddy/plutil. I've got those ready in separate packages - actool and re-plistbuddy respectively. I could:
- leave the broken versions in place (confusing)
- remove those from xcbuild
- include my reimplementations in xcbuild automatically
I'm leaning towards option 2 and let projects include specific tools as needed, but could be convinced otherwise. Do people have strong opinions here?
| 01:10:00 |
| viraptor | * Since I'm planning to fork xcbuild to include the bits needed for swift-build, I wanted to ask about the fate of tools in xcbuild conflicting with better implementations. Specifically xcbuild right now ships with buggy actool and not-quite-compatible PlistBuddy/plutil. I've got those in much better state and maintained in separate packages - actool and re-plistbuddy respectively. I could:
- leave the broken versions in place (confusing)
- remove those from xcbuild
- include my reimplementations in xcbuild automatically
I'm leaning towards option 2 and let projects include specific tools as needed, but could be convinced otherwise. Do people have strong opinions here?
| 01:10:45 |
| viraptor set a profile picture. | 01:20:34 |
