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
linuxPackages.bcc: 0.18.0 -> 0.19.0 #117043
Conversation
I'm not sure if this is in-scope for this bump, but one problem I noticed with linuxPackages.bcc is that when using it as a python module, it seemed like there were some import runtime dependencies on |
Result of 21 packages marked as broken and skipped:
1 package failed to build (new failures):1 package skipped due to time constraints:
9 packages built successfully:
1 suggestion:
Result of 10 packages marked as broken and skipped:
19 packages skipped due to time constraints:
25 packages built successfully:
1 suggestion:
|
This is going to be annoying to fix without a log; if you can provide a stack trace from somewhere, I'm happy to write a patch to |
@thoughtpolice: |
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 10 packages marked as broken and skipped:
44 packages built:
The following issues got detected with the above build packages.
linuxPackages.bcc:
warning: stale-substitute
|
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)