Skip to content

Staging next#50876

Merged
FRidh merged 160 commits intomasterfrom
staging-next
Nov 30, 2018
Merged

Staging next#50876
FRidh merged 160 commits intomasterfrom
staging-next

Conversation

@FRidh
Copy link
Member

@FRidh FRidh commented Nov 21, 2018

Motivation for this change
Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Fits CONTRIBUTING.md.

volth and others added 30 commits July 10, 2018 22:47
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>
[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.
@GrahamcOfBorg GrahamcOfBorg added 10.rebuild-darwin: 501+ This PR causes many rebuilds on Darwin and should normally target the staging branches. 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches. labels Nov 21, 2018
hunspell-1.7.0 broke enchant-1.6, upgrading to the latest 1.6 release fixes the
problem.
@hedning
Copy link
Contributor

hedning commented Nov 21, 2018

Updating enchant-1.6 fixed the issue. Pushed directly, hope that's okay.

@jtojnar jtojnar mentioned this pull request Nov 21, 2018
9 tasks
FRidh and others added 3 commits November 22, 2018 09:57
@Mic92 Mic92 mentioned this pull request Nov 24, 2018
10 tasks
@hedning
Copy link
Contributor

hedning commented Nov 25, 2018

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 pname changes @Synthetica9

@Synthetica9
Copy link
Member

@hedning #50364

@hedning
Copy link
Contributor

hedning commented Nov 26, 2018

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 -j 4) a bunch of times, but haven't seen a failure yet. Should we just turn off parallel building (it's not a huge build so not a big loss)?

@srhb srhb mentioned this pull request Nov 26, 2018
10 tasks
@GrahamcOfBorg GrahamcOfBorg added the 2.status: merge conflict This PR has merge conflicts with the target branch label Nov 28, 2018
valgrind: Apply upstream patch for Makefile race in coregrind
@Synthetica9
Copy link
Member

I've changed the base branch of #50364 from staging to staging-next, could someone give it a merge?

@GrahamcOfBorg GrahamcOfBorg removed the 2.status: merge conflict This PR has merge conflicts with the target branch label Nov 29, 2018
@hedning
Copy link
Contributor

hedning commented Nov 29, 2018

Okay, the main thing blocking staging-next is the version assert problem. There's two proposed fixes:

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?

c0bw3b and others added 3 commits November 29, 2018 23:48
version is set in lots of places but might not need to be in a name.

Alternative to #50364.
@FRidh
Copy link
Member Author

FRidh commented Nov 30, 2018

I pushed 28e2277 solving the version issue so we can merge this now.

@FRidh FRidh merged commit 2c5f92a into master Nov 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

6.topic: erlang General-purpose, concurrent, functional high-level programming language 6.topic: fetch Fetchers (e.g. fetchgit, fetchsvn, ...) 6.topic: GNOME GNOME desktop environment and its underlying platform 6.topic: golang Go is a high-level general purpose programming language that is statically typed and compiled. 6.topic: python Python is a high-level, general-purpose programming language. 6.topic: ruby A dynamic, open source programming language with a focus on simplicity and productivity. 6.topic: rust General-purpose programming language emphasizing performance, type safety, and concurrency. 6.topic: stdenv Standard environment 8.has: clean-up This PR removes packages or removes other cruft 8.has: documentation This PR adds or changes documentation 8.has: package (new) This PR adds a new package 10.rebuild-darwin: 501+ This PR causes many rebuilds on Darwin and should normally target the staging branches. 10.rebuild-darwin-stdenv This PR causes stdenv to rebuild on Darwin and must target a staging branch. 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-linux-stdenv This PR causes stdenv to rebuild on Linux and must target a staging branch.

Projects

None yet

Development

Successfully merging this pull request may close these issues.