We are migrating packages that meet below requirements:
1. using `callPackage`
2. called path is a directory
3. overriding set is empty (`{ }`)
4. not containing path expressions other than relative path (to
makenixpkgs-vet happy)
5. not referenced by nix files outside of the directory, other
than`pkgs/top-level/all-packages.nix`
6. not referencing nix files outside of the directory
7. not referencing `default.nix` (since it's changed to `package.nix`)
8. `outPath` doesn't change after migration
The tool is here: https://github.com/Aleksanaa/by-name-migrate.
Using shell to wrap is slow and not recommended, this alsos fixes issue
on aarch64-darwin sequoia 15.1.
Also auto sign kitty to prevent permission error on x86_64-darwin.
Restrict test execution inside nixosTests for Linux devices as ofborg
'passthru.tests' nixosTests are failing on Darwin architectures.
Ref: https://github.com/NixOS/nixpkgs/issues/345825
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
These tests were disabled because of failures on nix-darwin systems due
to zshenv producing spurious output in some scenarios:
https://github.com/LnL7/nix-darwin/pull/1051
The linked bug is fixed in nix-darwin, and it should be now possible to
run the tests on a fresh nix-darwin system.
Related: #312692
Since 648fd81e3e, contour has been
broken with what looks like a buffer overflow check failing.
The current version is also far behind upstream, and has
been broken on aarch64 for over a year.
Refs: #345752648fd81e3e
Signed-off-by: Christina Sørensen <christina@cafkafk.com>
In preparation for the deprecation of `stdenv.isX`.
These shorthands are not conducive to cross-compilation because they
hide the platforms.
Darwin might get cross-compilation for which the continued usage of `stdenv.isDarwin` will get in the way
One example of why this is bad and especially affects compiler packages
https://www.github.com/NixOS/nixpkgs/pull/343059
There are too many files to go through manually but a treewide should
get users thinking when they see a `hostPlatform.isX` in a place where it
doesn't make sense.
```
fd --type f "\.nix" | xargs sd --fixed-strings "stdenv.is" "stdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "stdenv'.is" "stdenv'.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "clangStdenv.is" "clangStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "gccStdenv.is" "gccStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "stdenvNoCC.is" "stdenvNoCC.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "inherit (stdenv) is" "inherit (stdenv.hostPlatform) is"
fd --type f "\.nix" | xargs sd --fixed-strings "buildStdenv.is" "buildStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "effectiveStdenv.is" "effectiveStdenv.hostPlatform.is"
fd --type f "\.nix" | xargs sd --fixed-strings "originalStdenv.is" "originalStdenv.hostPlatform.is"
```
