-
-
Notifications
You must be signed in to change notification settings - Fork 493
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
nixpkgs: backports from upstream #1318
Conversation
This might be redundant with the logs in the failing checks, but when I update my flake input I now get the following:
|
This got mangled in the backport a year and a half ago. Fixes: e25eeff
… externally This is a common footgun people hit often. Remove it. Backport of Nixpkgs commit ce87196a00214a0062ece1c3e03a9a97f563580f. Co-authored-by: K900 <[email protected]>
henrik-ch was also here :) Backport of Nixpkgs commit 11406bdc0e5af9b3c8a8d597da23349238c65277. Co-authored-by: Silvan Mosberger <[email protected]> Co-Authored-By: Valentin Gagarin <[email protected]>
system and config shouldn't both be specified — each will be filled in based on the other when the system is elaborated. Backport of Nixpkgs commit a3ba0495452cd8e72735ebd4472838e96902a259. Co-authored-by: Alyssa Ross <[email protected]>
921dcde
to
fb70457
Compare
Is it necessary for this PR to also reformat the entire file? It makes it very hard to see what the actual change is... |
fb70457
to
537056b
Compare
Yes, since Nixpkgs upstream formatted it and it’s necessary to easily backport the changes after that point. We should do a treewide reformat but I’m holding out until Nixpkgs does the full treewide. I will add the reformatting commit to All the changes here are just backported from NixOS. If you want to review the backports I’d suggest going commit‐by‐commit, since otherwise you’re reading like ten upstream PRs at once. |
Since the output of `lib.systems.elaborate` contains functions, an equality check with `==` does not suffice, `lib.systems.equals` should be used instead. Backport of Nixpkgs commit 3794246066409d7baac72e3fdfb0e4f66ef4a013. Co-authored-by: Jared Baur <[email protected]>
Backport of Nixpkgs commit e6057cfd59f278db3aeb058a4e1e0bcc24696267. Co-authored-by: Valentin Gagarin <[email protected]> Co-authored-by: Dominic Mills <[email protected]>
Backport of Nixpkgs commit 609e57485d1fa111e3a689498d9d338dc03a7bc5. Co-authored-by: Felix Buehler <[email protected]>
The assertion message should include the `nixpkgs.config` value, however it currently includes the entire `nixpkgs.config` _option_. This means the type, declarations, definitions, etc were all printed. Backport of Nixpkgs commit 1bd4da1848cb7b68858ebb2ca1f8b0e5fed46c58. Co-authored-by: Matt Sturgeon <[email protected]>
Backport of Nixpkgs commit 6d9dfef94ffd59a327573eea7bc709a84c44b3d2. Co-authored-by: Matt Sturgeon <[email protected]>
The description for options.nixpkgs.system already hints at this: Neither ${opt.system} nor any other option in nixpkgs.* is meant to be read by modules and configurations. Use pkgs.stdenv.hostPlatform instead. We can support this goal by not elaborating the systems anymore, forcing users to go via pkgs.stdenv. This will prevent problems when making the top-level package sets composable in the next commit. For this to work, you should pass a fully elaborated system to nixpkgs' localSystem or crossSystem options. Backport of Nixpkgs commit 0a19371146130c0e2a402fd0c35f8283b0e81910. Co-authored-by: Wolfgang Walther <[email protected]>
Ditto, but only if I have If I set it true, I get the following:
This goes away if I manually set:
It isn't obvious to me why the default isn't working. |
@wolfgangwalther Looks like |
537056b
to
7c72c01
Compare
Actually I guess we can do |
Thanks for the quick turnaround. I did the following:
and I get the following:
am I doing something wrong? |
Not sure. Seems like the Linux builder is trying to build part of your nix-darwin configuration (I guess?) but I don’t know why. |
No, I don't think so. This piece of
|
Yeah, I think that in messing around with different branches and configs I worked my machine into a state where linux-builder was being told to build stuff it's not supposed to. Could've been my "workaround" above broke things. Unsure. I reset things to an older state and then tried again. Things seem to work now. Relevant entries from my flake.lock, in case these are useful:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not the biggest fan of the last commit as it's unclear of it's going to get reverted (see NixOS/nixpkgs#376988 (comment))
However, according to @wolfgangwalther it should still be backwards compatible (NixOS/nixpkgs#376988 (comment)) so I'm going to merge this now
to bring in LnL7/nix-darwin#1318
Let me clarify my comment: I was mostly thinking about two scenarios:
The fixes for those will be unproblematic, now that we had a revert. I am not sure that this applies to the change in this PR, though: I still can't wrap my head around the "copying of the whole module", but I can imagine that you will get similar breakage now with this version in nix-darwin and the revert upstream. So... better be prepared to apply the reverted changes here as well. |
Should fix the module after recent Nixpkgs changes.