-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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
python: coverage: 4.5.4 -> 5.1 #87430
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since this change causes over 500 rebuilds, do you mind targeting the staging branch
git rebase --onto=origin/staging HEAD~1
git push .. ... --force
then change the base branch in the github PR from master
-> staging
See https://nixos.org/nixpkgs/manual/#submitting-changes-staging-branch for more details on staging branch
Sorry, my fault. Rebased. |
Is there any way one can check the number of rebuilds in advance? |
You can do a |
@GrahamcOfBorg build python3Packages.requests |
looks like there's a major regression with cffi in staging right now |
This update should be fine by now. If it turns out it breaks (too many) Python packages, we revert in staging-next. |
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)