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
sip_5: init at 5.5.0 #108041
sip_5: init at 5.5.0 #108041
Conversation
Result of 5 packages marked as broken and skipped:
17 packages failed to build:
137 packages built:
|
Result of 19 packages marked as broken and skipped:
70 packages failed to build:
3 packages built:
|
Regarding x86_64-linux, it seems that all failing packages are broken upstream (except koboredux, which needs manually-provided files). Regarding x86_64-darwin, looking at the log seems that there are also packages broken upstream. |
Result of 5 packages marked as broken and skipped:
15 packages failed to build:
139 packages built:
|
This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch) Result of 17 packages marked as broken and skipped:
20 packages failed to build and are new build failures:
55 packages built:
The following issues got detected with the above build packages. kcc: Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
|
Added |
Looking at the logs of the darwin build:
Seems to be unrelated.
Might be related. Does it build on master?
According to this,
Not very helpful... |
nope and no idea why. gnuradio: https://hastebin.com/raw/alabijapef |
Seems unrelated too (gtk dependency not detected) |
Result of 5 packages marked as broken and skipped:
16 packages failed to build:
136 packages built:
VTK is already broken on master. |
Motivation for this change
Adds sip5 and changes pyqt5 to use sip5 instead of sip4. This is needed to build calibre 5.
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)