New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zen-kernels: 5.11.13 -> 5.11.14 #119520
zen-kernels: 5.11.13 -> 5.11.14 #119520
Conversation
7c65983
to
87e6675
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch). Result of 20 packages marked as broken and skipped:
28 packages failed to build and already failed to build on hydra master:
63 packages failed to build and are new build failures:
62 packages built:
|
I would appreciate it if you could mark modules which do not work as broken for zen-kernels. |
They aren't broken for zen-kernels, they're broken for every 5.11 kernel we ship. |
Maybe we should mark them all broken for 5.11 if they are broken for the foreseeable future. |
Yeah as I said last time, haven't found the time to do that yet. Ideally, modules should be marked as broken whenever a new kernel is introduced, no idea why that's not being done already. |
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)