7 ms·
In practice nix-darwin relies on being a drop in, which means maintaining compatibility with api surface which in the proper nixpkgs world is a closed loop. The
by dayjah 10mo ago
In practice nix-darwin relies on being a drop in, which means maintaining compatibility with api surface which in the proper nixpkgs world is a closed loop. There are several cases of this breaking since 2020 or so.
- viraptor 10mo agoBut did that happen while updating from the same stable channel? I get things could change when switching releases.
- dayjah 10mo agoPretty sure I just ran a nix flake update. Here are the links from my journal: This went into nixpkgs: https://github.com/NixOS/nixpkgs/pull/376988 https://github.com/NixOS/nixpkgs/pull/376988 Which then changed the api between and broke this: https://github.com/LnL7/nix-darwin/blob/master/modules/nix/nixpkgs.nix https://github.com/LnL7/nix-darwin/blob/master/modules/nix/n... The fix took a few hours, I happened to be one of the first folks bit by it: https://github.com/LnL7/nix-darwin/pull/1318 https://github.com/LnL7/nix-darwin/pull/1318 I also have in my notes that Emilazy is a super star: https://github.com/emilazy https://github.com/emilazy Notes on how I worked around it for the time it was broken: > To work around it on myside I tried various things. Fundamentally I rolled back to nixpkgs-24.11-darwin which needed corresponding changes to nix-darwin (nix-darwin-24.11) and home-manager (release-24.11) to get everything working.