-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
jupyter update 2024-06-08 #318251
jupyter update 2024-06-08 #318251
Conversation
Result of 64 packages marked as broken and skipped:
30 packages failed to build:
129 packages built successfully:
Result of 17 packages marked as broken and skipped:
5 packages failed to build:
230 packages built successfully:
Result of 17 packages marked as broken and skipped:
4 packages failed to build:
231 packages built successfully:
Result of 64 packages marked as broken and skipped:
8 packages failed to build:
151 packages built successfully:
|
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.
Diff LGTM
I would argue to get broken packages marked as such. (Of course, one needs to check if there is any regression first). |
There is no regression. |
Description of changes
Update jupyter-related packages at once to avoid building hundreds of packages over and over again.
This PR is based on the commits generated by the following command.
closes #319226
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.