Given the prior attempts to encourage Nix package bumps to be more stable, we failed, failed and failed again.
Today again, we shipped a broken Nix (2.19.2) without sufficient testing to unstable-small and it broke some users.
As announced in the past, I am taking ownership of the package manager bumps and modifications
as seemingly no one is interested to do it inside of Nixpkgs.
This re-introduces the old stable ZFS version we had in the past following
the many predicted issues of ZFS 2.2.x series, that is much more stable
than any further ZFS version at the moment.
I am also removing myself from maintenance of any further ZFS versions as I am
planning to quit ZFS maintenance at some point.
In the meantime, for users like me who depend on ZFS for critical operations, here is a ZFS version
that is known to work for LTS kernels.
This introduces the `pkgs/by-name` directory as proposed by RFC 140.
Included are:
- The implementation to add packages defined in that directory to the
top-level package scope
- Contributer documentation on how to add packages to it
- A GitHub Actions workflow to check the structure of it on all PRs
I want to take ownership of this part of the documentation, especially
with the cleanup in https://github.com/NixOS/nixpkgs/pull/245243. Doing so
before that PR is merged also allows me to get notified about any potential
future merge conflicts before they happen.
It is hard to get people to test changes to our kernel expression on
anything other than x86_64 and aarch64 before merging changes.
Therefore, I would like to be notified of PRs opened agains this
file, so that I can hopefully catch breakage before it is merged,
rather than afterwards.
I don't claim ownership of anything, but I would like to be notified
of PRs opened against the following paths where I've put a lot of
work into cleanup and deduplication:
lib/systems
pkgs/stdenv
pkgs/build-support/cc-wrapper
pkgs/development/compilers/gcc
Apparently CODEOWNERS is how you tell github you want to be notified
of such things.
