| 14 Jan 2026 |
 raitobezarius | i have no idea yet how we are going to overcome this | 14:18:05 |
 ginkogruen | Maybe I’ll pin lix then until it’s fixed. | 14:18:17 |
| raitobezarius | it's not a lix regression alas | 14:18:27 |
| raitobezarius | what Lix (and Nix) have been doing has always been considered unsafe to some extent by macOS I think | 14:18:44 |
| raitobezarius | recent macOS upgrades started to exhibit breakage harder | 14:18:52 |
| raitobezarius | sufficiently so that everyone runs into it from time to time | 14:18:58 |
| raitobezarius | it unfortunately also extend to nix-shell -p itself | 14:19:14 |
| ginkogruen | Oh then I’ve misunderstood what this build failure is about. | 14:19:20 |
| raitobezarius | (or any runCommand primitive) | 14:19:23 |
| raitobezarius | I'm not sure neither what it is, but there's an ongoing major problem with macOS related to the execution of anything without a shebang, we fixed many of those but nix-shell-based workloads are broken and we test many things in the testsuite | 14:19:59 |
| raitobezarius | (are broken non-deterministically, that is, they work N % of the time) | 14:20:16 |
| ginkogruen | Oh macOS could you please just work and not cause issues.
Thanks for the info I’ll guess then I’ll either run the slot machine or disable checks.
Thanks for looking into it or at least trying to come up with a fix to this. | 14:23:32 |
| raitobezarius | https://git.lix.systems/lix-project/lix/issues/1101 | 14:26:01 |
| raitobezarius | I assembled this quickly | 14:26:04 |
| raitobezarius | This is now pinned | 14:26:16 |
| raitobezarius | if we figure out a fix, we will send it to all released Lix versions as well | 14:27:00 |
| raitobezarius | tbh, it's also kinda our historical fault but heh | 14:27:16 |
