-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Mark failing to build packages in 20.09 as broken #100111
Comments
@petabyteboy made https://github.com/NixOS/nixpkgs/blob/master/pkgs/common-updater/scripts/mark-broken for us last release so we can try the script out this release. Having this happen on a regular automated basis would be nicer, though. |
Will it be possible to ping the maintainers of the respective packages? |
Manually, probably humanly impossible 😁 If they are in nixpkgs-maintainers ofborg should handle it. |
I would also say that the appropriate time to fix a package was during ZHF. That being said, fixes are always welcome. Packages that fail to build can be found by maintainer by running:
example:
|
ofborg only requests reviews from a maximum of 9 people; else, it skips this. So, maybe not. |
@grahamc What's the reason for that limit? Could it be lifted or would that lead to problems? |
The reason is so we don't ping the entire list when staging and staging-next PRs are opened. EDIT: And there's probably an API limitation somewhere in there. |
This is partially done. Only linux modules should be left:
|
the kernel modules have been appropriately marked broken. |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/policy-on-marking-packages-as-broken/9861/2 |
Describe the bug
As Per ZERO Hydra Failure #80379, we're supposed to mark every package that fails to build on the stable branch as broken. People can backport fixes to unbreak packages after we cut the final release. This is best done all at once semi-automatically, so this will be a task for @NixOS/nixos-release-managers to perform when they are about to cut the final release. (in a PR please ❗ )
The text was updated successfully, but these errors were encountered: