Hydra passes the full revision in to the input, which we pass through.
If we don't get this ,we try to get it from other sources, or default to
master which should have the definition in a close-ish location.
All published docs should have theURL resolve properly, only local
hackers will have the link break.
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.
This commit removes all references to emacs24 with the exception of
emacs24-macports. The two folders in `pkgs/applications/editors` named
`emacs-24` and `emacs-24` are consolidated to a new `emacs` folder.
Various parts in nixpkgs also referenced `emacs24Packages` (pinned to
`emacs24`) explicitly where `emacsPackages` (non-pinned) is more
appropriate. These references get fixed by this commit too.
not part of nixpkgs/nixos jobsets in 16.03+ since ccd1029f58. Until
it gets added again, adding some python packages that take really
long to build.
(cherry picked from commit 713c240563)
From now on, only the testing branch of grsecurity will be supported.
Additionally, use only patches from upstream.
It's impossible to provide meaningful support for grsecurity stable.
First, because building and testing \(m \times n \times z) [1], packages
is infeasible. Second, because stable patches are only available from
upstream for-pay, making us reliant on third-parties for patches. In
addition to creating yet more work for the maintainers, using stable
patches provided by a third-party goes against the wishes of upstream.
nixpkgs provides the tools necessary to build grsecurity kernels for any
version the user chooses, however, provided they pay for, or otherwise
acquire, the patch themselves.
Eventually, we'll want to remove the now obsolete top-level attributes,
but leave them in for now to smoothe migration (they have been removed
from top-level/release.nix, though, because it makes no sense to have
them there).
[1]: where \(m\) is the number of grsecurity flavors, \(n\) is the
number of kernel versions, and z is the size of the `linuxPackages` set
This cuts nixpkgs:trunk from 78K to 31K jobs by disabling builds of
{node,go,python,emacs,coq,r,ocaml,perl}Packages. Thus these are now
only built if they are dependencies of top-level packages (such as
end-user applications). I left haskellPackages because they take
typically longer to build than the others (which are mostly
interpreted languages), so disabling them would be more painful to
users.
This is a temporary measure until we have a binary cache based Hydra
running on faster hardware, necessitated by the fact that evaluations
now regularly time out after 6 hours.
The R people don't bother providing stable URLs for their package
releases. Released versions are edited or flat-out disappear at will,
which causes us a bit of trouble, like in [1]. Hopefully, enabling R
builds on Hydra will mitigate those problems by caching the release
tarballs.
[1] https://github.com/NixOS/nixpkgs/issues/11230
