Open aherrmann opened 1 year ago
Opened an upstream issue: https://github.com/NixOS/nixpkgs/issues/270375
This seems to be caused by this PR https://github.com/NixOS/nixpkgs/pull/235990 which is (somewhat ironically) titled "nixStatic: Fix darwin".
The bottom line is that before that change coreutils
and pkgsStatic.coreutils
were exactly the same on Darwin:
$ nix-shell -I nixpkgs=./. --pure -p which pkgsStatic.coreutils --run 'which tsort'
/nix/store/3acj5l3cwmliiihig0hm6y4p0nsk8jgi-coreutils-9.1/bin/tsort
$ nix-shell -I nixpkgs=./. --pure -p which coreutils --run 'which tsort'
/nix/store/3acj5l3cwmliiihig0hm6y4p0nsk8jgi-coreutils-9.1/bin/tsort
Describe the bug Updating the nixpkgs revision from https://github.com/NixOS/nixpkgs/commit/ea4c80b39be4c09702b0cb3b42eab59e2ba4f24b (NixOS 22.11) to https://github.com/NixOS/nixpkgs/commit/6500b4580c2a1f3d0f980d32d285739d8e156d92 (nixos-unstable at the time of writing) breaks the import of
pkgsStatic.coreutils
on MacOS 11 on x86_64, see this CI failure.The same tests succeed on an arm64 MacOS machine.
To Reproduce Update the nixpkgs revision used in the rules_nixpkgs tests as described above and run the tests in the top-level WORKSPACE on MacOS 11 x86_64.
Expected behavior The tests should pass on MacOS x86_64 with
pkgsStatic.coreutils
as they did before the nixpkgs update. This may very well be an upstream nixpkgs issue. However, at this point I don't have enough information to raise a meaningful issue on nixpkgs itself. So, I'm opening this issue first.Environment
Additional context This issue surfaced in the context of https://github.com/tweag/rules_nixpkgs/pull/423 and can be worked around by not using
pkgsStatic
on MacOS.