- tracing seems annoying enough
- we get errors for all packages instead of aborting on the first one
- easier to differentiate from unwanted packages (broken, unfree, etc.)
Another test issue surfacing from the setuptools bump in
70c189976809dfdcedee4a9a69558866c1ff95a1.
This time, the tests just fail because mock is missing as a dependency.
Tested building against Python 2.7 and Python 3.6.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @joachifm, @Mic92
The bump of setuptools from version 36.7.1 to 38.2.3 (commit
70c189976809dfdcedee4a9a69558866c1ff95a1) has caused the axolotl tests
to suddenly being run.
As the comment prior to the doCheck attribute states, we're using
pycryptodome so the tests are expected to fail even on Python 2.7 but
because of the version bump mentioned above, the tests didn't run and
thus the build didn't fail during when commit
094ac2d9b1d3c6895a9c9e0e4401919c475f4f2c was made.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @abbradar, @Mic92
Built successfully on x86_64-linux.
I've verified the contents of the tarball by comparing its contents
against the tag of my local checkout. Furthermore, I've checked the GPG
signature of the tag.
Signed-off-by: aszlig <aszlig@nix.build>
Since keeping `installPhase = ""` to signify "use the default installPhase" will
be surprising, this deletes the installPhase and rebuilds qt4 on all platforms.
Fixes#30238
28299f669adc41e5278372cad952fb1e1165b44b introduced the first Python
packages having multiple outputs. The required outputs were not picked
up by `python.buildEnv` (#31857).
This commit modifies `python.buildEnv` so that it always includes the
$out output and thus fixes#31857.
`bash-completion` lazy loads completion scripts by looking up the command name
in the completion directory. As such we need to create a symlink for every
nix command.
The problem had been masked by nixos sourcing all completion scripts on startup.
