These are some parts of the release that I want to get working before
we release 18.09. There have been lots of improvements since 18.03 (as
well as some regressions). To make sure the release is well-tested we
need to add these apps in the jobset. Most of these are UI apps that
are now available.
List of new apps added to the release:
- wireshark
- firefox
- qtmultimedia (already in unstable)
- inkscape (already in unstable)
- gimp
- wireshark
- transmission
Also add ‘stack’. This is one of the Haskell packages hitting the
ARG_MAX limit on macOS (getconf ARG_MAX == 262144). This has not been
solved yet but it will need to be resolved by 18.09. Making it block
here will prevent this regression in the future.
[squashed] release: remove broken from darwin-tested
removes:
- gimp
- qtmultimedia
This reverts commit 0d8076b99c.
This has been causing people issues so it’s easiest to leave it off
for now. Eventually I will do an RFC or some other PR where we can
have more discussion on benefits of doing this in CI.
Fixes #44299
I still think it’s still worth keeping aliases out of Nixpkgs but we
don’t need to block evaluation on it.
This reverts commit 25c42e7736.
This commit is still causing evaluation errors (despite passing
OfBorg!)
Here is the current error:
error: undefined variable 'Log4Perl' at
/nix/store/n0gwyv3mcvm3hc9jrmkxjhmsrdjqzcqb-source/maintainers/scripts/nix-generate-from-cpan.nix:7:71
More investigation is needed
/cc @volth
This reverts commit 67d0a57ef9.
which caused evaluation errors in restricted eval mode, producing:
error: access to URI
'/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/mr-est/eval-1-lassulus.ewr1.nix.ci' is
forbidden in restricted mode
nix-repl is not needed anymore because Nix 2.0 comes with repl already. Anyway nix-repl is broken right now on Hydra because Nix 1.11 is broken.
https://hydra.nixos.org/build/74933091
13d6681ce7 crippled it unintentionally.
Also remove the incorrect/non-existing stdenv.i686-linux;
building the bootstrap tools should be a good-enough test anyway.
13d6681ce7 crippled it unintentionally.
Also remove the incorrect/non-existing stdenv.i686-linux;
building the bootstrap tools should be a good-enough test anyway.
The old hard-coded lists are now used to test system parsing.
In the process, make an `assertTrue` in release lib for eval tests; also
use it in release-cross
This allows customizing the nixpkgs arguments by the caller. My use case
is creating a personal nixpkgs channel containing some unfree packages.
The default is still to not build unfree packages, so for nixpkgs this
is no functional change.
