-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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
Staging next #50876
Staging next #50876
Conversation
This reverts commit 9c4b11e.
In strictDeps=false, autoPatchshebangs should use --build (corresponding to PATH) to lookup commands. This restores the previous behavior of patchshebangs so that we don’t break stuff that isn’t careful in the buildInputs vs. nativeBuildInputs distinction. Unfortunately this won’t work under cross compilation.
patch shebangs needs to be in build inputs for it to get into HOST_PATH.
This is because it gets passed to mkDerivation through some route, this ensures that doesn't mess with anything
Co-Authored-By: Synthetica9 <git@hilhorst.be>
Co-Authored-By: Synthetica9 <git@hilhorst.be>
See http://lists.gnu.org/archive/html/info-gnu/2018-11/msg00003.html for release information
[WIP] Implement RFC0035 II: Electric Boogaloo
This includes fixes for CVE-2018-10754. While we're changing things, also set the `--with-manpage-format=normal` configure flag, which prevents the `configure` script from looking in /usr to determine whether to compress manpages. This was already the format on NixOS (where these directories don't exist), but making this explicit makes the build more reproducible on other distros.
hunspell-1.7.0 broke enchant-1.6, upgrading to the latest 1.6 release fixes the problem.
Updating enchant-1.6 fixed the issue. Pushed directly, hope that's okay. |
Upstream bug: curl/curl#3218. This causes nixos/tests/ipv6.nix to fix since the last staging merge.
There's something wrong with the tarballs: https://hydra.nixos.org/build/84759686 I'm getting the same problem when trying to build a VM. Looks like it's connected to the default |
valgrind seems to fail randomly (I've seen the same failure on staging and trunk a few times now), Tried reproducing the failure locally (with |
valgrind: Apply upstream patch for Makefile race in coregrind
I've changed the base branch of #50364 from |
Okay, the main thing blocking staging-next is the
If #51183 is a massive rebuild (not sure how changes to mkDerivation works or if ofBorg picks them up) I'd say we should merge #50364 here first, and wait for the next merge window to add #51183. If it's not a massive rebuild I'd say we go for #51183 directly. Does that sound fair? |
version is set in lots of places but might not need to be in a name. Alternative to #50364.
I pushed 28e2277 solving the |
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)