4 ms·

Unfortunately, Nixpkg doesn't check buildability on Darwin when merging PRs, so things can break quite often on the nixpkgs-unstable channel (compared to nixpkg

by sirn 6y ago

Unfortunately, Nixpkg doesn't check buildability on Darwin when merging PRs, so things can break quite often on the nixpkgs-unstable channel (compared to nixpkgs-unstable on Linux). It's not hard to rollback, though, but it does makes me never want to ever run `nix-channel --update`.

Ericson2314 6y ago
Use one of the Darwin channels, that won't advance unless Darwin things are not too broken.
abathur 6y ago
I feel similarly and am a little careful about when I choose to take an update. That said, I think most people want darwin failures to be able to block, so it's mostly about getting on top of them to the point where it's practical to keep them triaged. Domen is working on getting a part-time position funded to work on issues here (https://opencollective.com/nix-macos https://opencollective.com/nix-macos), though individual package breaks are probably down the list.
soraminazuki 6y ago
nixpkgs CI does check for buildability on Darwin, which can be confirmed by looking at any of their PRs. However, packages do tend to be get marked as broken on Darwin if it doesn’t build and the packager doesn’t own a Mac. I feel things have stabilized significantly in recent days, though. I haven’t had a single Darwin breakage on the unstable channel since the release of 20.09. Perhaps the Zero Hydra Failures effort[1] helped. [1]: https://github.com/NixOS/nixpkgs/issues/97479 https://github.com/NixOS/nixpkgs/issues/97479
- sirn 6y ago
  I think what I meant was darwin failure doesn't block. Recently I had nomad breakage on -unstable caused by nvml support, which pulls in nvidia_x11, which pulls in linux_5_4, which of course not installable on darwin[1]. The maintainer fixed it very quickly (thank you!) but I still need to wait few more days for it to be included in -unstable. [1]: https://github.com/NixOS/nixpkgs/issues/108603 https://github.com/NixOS/nixpkgs/issues/108603

by sirn 6y ago

Ericson2314 6y ago

Use one of the Darwin channels, that won't advance unless Darwin things are not too broken.

abathur 6y ago

I feel similarly and am a little careful about when I choose to take an update. That said, I think most people want darwin failures to be able to block, so it's mostly about getting on top of them to the point where it's practical to keep them triaged. Domen is working on getting a part-time position funded to work on issues here (https://opencollective.com/nix-macos https://opencollective.com/nix-macos), though individual package breaks are probably down the list.

soraminazuki 6y ago

nixpkgs CI does check for buildability on Darwin, which can be confirmed by looking at any of their PRs. However, packages do tend to be get marked as broken on Darwin if it doesn’t build and the packager doesn’t own a Mac. I feel things have stabilized significantly in recent days, though. I haven’t had a single Darwin breakage on the unstable channel since the release of 20.09. Perhaps the Zero Hydra Failures effort[1] helped. [1]: https://github.com/NixOS/nixpkgs/issues/97479 https://github.com/NixOS/nixpkgs/issues/97479

sirn 6y ago
I think what I meant was darwin failure doesn't block. Recently I had nomad breakage on -unstable caused by nvml support, which pulls in nvidia_x11, which pulls in linux_5_4, which of course not installable on darwin[1]. The maintainer fixed it very quickly (thank you!) but I still need to wait few more days for it to be included in -unstable. [1]: https://github.com/NixOS/nixpkgs/issues/108603 https://github.com/NixOS/nixpkgs/issues/108603