| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|
|
|
|
| |
2.4 has its own completion script which collides with
nix-bash-completions.
|
|
|
|
|
|
|
| |
This reverts commits 9d0de0dc57ce97ab9cc3d73a66e914d718e4af3b,
27d2857a9927aa197b9679b9a2dcf59b97c06907. 'nix ping-store' is an
experimental command so it doesn't work in Nix 2.4 unless you set
'experimental-features = nix-command' in nix.conf.
|
|
|
|
|
| |
tarballs.nixos.org is omitted from the change because urls from there
are always hashed and checked
|
|
|
|
|
|
|
|
| |
This reverts commit 5291925fd2486175e781669412fa5a525da7602a.
Reason: This started to cause severe regressions, see:
- https://github.com/NixOS/nixpkgs/issues/85552
- https://github.com/NixOS/nixpkgs/pull/83166#pullrequestreview-395960588
Fixes #85552.
|
|
|
|
|
| |
Allow to specify where package build will happens.
It helps big packages (like browsers) not to overflow tmpfs.
|
| |
|
|
|
|
|
| |
Instead of making the configuration less portable by hard coding the number of
jobs equal to the cores we can also let nix set the same number at runtime.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows you to specify the system-wide flake registry. One use is
to pin 'nixpkgs' to the Nixpkgs version used to build the system:
nix.registry.nixpkgs.flake = nixpkgs;
where 'nixpkgs' is a flake input. This ensures that commands like
$ nix run nixpkgs#hello
pull in a minimum of additional store paths.
You can also use this to redirect flakes, e.g.
nix.registry.nixpkgs.to = {
type = "github";
owner = "my-org";
repo = "my-nixpkgs";
};
|
| |
|
|
|
|
|
|
|
|
| |
A centralized list for these renames is not good because:
- It breaks disabledModules for modules that have a rename defined
- Adding/removing renames for a module means having to find them in the
central file
- Merge conflicts due to multiple people editing the central file
|
| |
|
|
|
|
|
|
| |
The `gc-` prefixed versions of these options have been
deprecated since Nix 2.0.
|
| |
|
| |
|
|
|
|
| |
Probably didn't work anyway anymore.
|
|
|
|
|
|
|
| |
In fact, don't create them at all because Nix does that automatically.
Also remove modules/programs/shell.nix because everything it did is
now done automatically by Nix.
|
|
|
|
|
|
|
| |
Since version 2.3 (https://github.com/NixOS/nix/pull/2949 which was
cherry-picked to master) Nix issues a warning when --no-net wasn't
passed and there is no network interface. This commit adds the --no-net
flag to the nix.conf check such that no warning is issued.
|
|\ |
|
| |
| |
| |
| | |
For security, we don't want the sandbox to be disabled silently.
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are many support questions when people add a new binary cache
and they suddenly lose nixos substitutions.
Most of the users want to keep that, so we're doing a breaking change.
Previously to disable all binary caches one had to do:
nix.binaryCache = [];
Now the same is possible via:
nix.binaryCache = lib.mkForce;
|
|
|
|
| |
following up #59148
I forgot the default case of the architectures which do not have minor brothers whose code they can run ("westmere" or any of of AMD)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
These days build systems are more robust w.r.t. to concurrency.
Most users will have at least two cores in their machines.
Therefore I suggest to increase the number of cores used for building.
fixes #50376
|
|
|
|
|
|
|
|
| |
* nixos/nix: ignore nix.checkConfig when cross-compiling
the check always fails because of architecture mismatch
* typos
|
|\
| |
| | |
nix-daemon service: Ensure `ssh` is on PATH. Fixes #46038.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes a regression introduced in commit
700e21d6dac4683ef40f20127a6eb2a74b9bd8c6
nix needs ssh on path for the SSH substituter functionality,
not only the distributed builds functionality.
Signed-off-by: Niklas Hambüchen <mail@nh2.me>
|
| |
| |
| |
| | |
Per reviewer comment (thanks!).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
environment.sessionVariables cannot refer to the values of env vars,
and as a result this has caused problems in a variety of scenarios.
One use for these is that they're injected into /etc/profile,
elewhere these are used to populate an 'envfile' for pam
(`pam 5 pam_env.conf`) which mentions use of HOME being
potentially problematic.
Anyway if the goal is to make things easier for users,
simply do the NIX_PATH modification as extraInit.
This fixes the annoying problems generated by the current approach
(#40165 and others) while hopefully serving the original goal.
One way to check if things are borked is to try:
$ sudo env | grep NIX_PATH
Which (before this change) prints NIX_PATH variable with
an unexpanded $HOME in the value.
-------
This does mean the following won't contain user channels for 'will':
$ sudo -u will nix-instantiate --eval -E builtins.nixPath
However AFAICT currently they won't be present either,
due to unescaped $HOME. Unsure if similar situation for other users
of sessionVariables (not sudo) work with current situation
(if they exist they will regress after this change AFAIK).
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 67c8c4917799496dcf2ad6a500441fbbaeb918c9.
'nix run nixos.firefox' is *not* supposed to work - the Nix 2.x
interface attempts to standardize on nixpkgs.*, to get rid of the
nixos/nixpkgs confusion that existed with the channels interface. So
let's not bring that confusion back.
|
|/
|
|
|
|
|
|
|
| |
This makes using the nixos channel work out of the box with the new
Nix commands. For example:
$ nix run nixos.firefox -c firefox
Fixes #46536
|
|\
| |
| | |
nixos/nix-daemon: build-max-jobs, add support to auto
|
| | |
|
|/ |
|
| |
|
|
|
|
| |
This was put together based on feedback from LnL on IRC.
|
|\ |
|
| |
| |
| | |
Ideally I'd like the whole `nixos`/`nixpkgs` channel distinction to disappear, but this is a step along that path. After a while being in this state, we can stop creating the magic `nixpkgs -> .` symlink inside our `nixos` channel tarballs and simplify that whole mess a bit.
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* checks using package providing the nix-daemon that we'll be using
* made optional (unlike some other config checks) "just in case":
since this requires running the new Nix on the builder, this
won't work in a few (AFAIK very uncommon) situations such as
cross-compiling NixOS or using `include` directives in nix.conf
This does rely on Nix2 but not by the builder.
Since we only offer Nix2+ in-tree this should be fine,
and may otherwise be required anyway.
|
|\ \
| |/
|/| |
Add user channels to the default nix path
|
| | |
|
|/
|
|
| |
Fixes #38421.
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Resolved the following conflicts (by carefully applying patches from the both
branches since the fork point):
pkgs/development/libraries/epoxy/default.nix
pkgs/development/libraries/gtk+/3.x.nix
pkgs/development/python-modules/asgiref/default.nix
pkgs/development/python-modules/daphne/default.nix
pkgs/os-specific/linux/systemd/default.nix
|