!lheuhImcToQZYTQTuI:nixos.org

Nix on macOS

1206 Members
“There are still many issues with the Darwin platform but most of it is quite usable.” — http://yves.gnu-darwin.org202 Servers

Load older messages


SenderMessageTime
23 Apr 2026
@reckenrode:matrix.orgRandy EckenrodeAPFS 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
@reckenrode:matrix.orgRandy EckenrodeI think that’s the same as btrfs and ZFS.18:32:31
@toonn:matrix.orgtoonn Btrfs used to have such a problem but reserves some space to always be able to delete something now I think. 19:54:18
@sarahec:matrix.orgSarah 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
@reckenrode:matrix.orgRandy EckenrodeDoes it build a native extension? If so, I guess that could end up with a bad signature.23:17:19
@sarahec:matrix.orgSarah ClarkIt's definitely using Cython23:19:06
@reckenrode:matrix.orgRandy EckenrodeIs this on staging or master?23:20:19
@sarahec:matrix.orgSarah Clarkmaster23:20:27
@reckenrode:matrix.orgRandy EckenrodeStaging got linker upgrade. (though I doubt it will help.)23:20:51
@sarahec:matrix.orgSarah ClarkI 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:tchncs.deviraptor

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:tchncs.deviraptor *

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:tchncs.deviraptor *

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:tchncs.deviraptor set a profile picture.01:20:34
@nor1nco:matrix.orgNorincoI found that after updating nixpkg, the permissions granted in the macOS settings will be invalid. Is there any good solution to this problem?08:54:22
@bestlem:matrix.orgbestlem

direnv is failing on nixpkgs-unstable https://github.com/NixOS/nixpkgs/issues/513019
I note from the isuue that

Can Hydra reproduce this build failure?

The last build job was manually cancelled.

Does this mean that failure on direnv builds for darwin can be ignored and we get a broken nikpkgs - or is this just a one off manual error?
The error looks like a timeout

10:06:02
19 May 2021
@grahamc:nixos.org@grahamc:nixos.org set the history visibility to "world_readable".19:22:35
@grahamc:nixos.org@grahamc:nixos.org changed the room name to "" from "".19:22:35
@0x4a6f:matrix.org[0x4A6F] joined the room.19:23:06
@nbardiuk:matrix.orgnazarii joined the room.19:24:29
@casey:hubns.netcasey © joined the room.19:27:39
@elvishjerricco:matrix.orgElvishJerricco joined the room.19:38:47
@andi:kack.itandi- joined the room.19:39:40
@stick:matrix.orgstick joined the room.19:46:16
@server_stats:nordgedanken.devServer Stats Discoverer (traveler bot) joined the room.19:50:54
@joerg:bethselamin.deMic92 joined the room.19:51:07
@voyager:t2bot.ioMatrix Traveler (bot) joined the room.20:03:59
@gaelans:matrix.orgGaelan Steele joined the room.20:16:00
@cgbrewster:matrix.orgcgbrewster joined the room.20:17:23
@gaelans:matrix.orgGaelan Steele changed their display name from gaelans to Gaelan Steele.20:24:29

Show newer messages


Back to Room ListRoom Version: 6