| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Not entirely sure when it got broken this time, but when creating a VM
network with `nixos-build-vms(8)`, there are should be the following scripts:
* `$out/bin/nixos-test-driver` which drops into an interactive shell to
interactively perform test steps.
* `$out/bin/nixos-run-vms` which non-interactively starts the VMs from
the network so that one can manually play around in the VM.
The latter also starts an interactive shell for a while now which means
that it does the exact same thing as `nixos-test-driver` which is not
its purpose.
|
|
|
|
| |
hardware-configuration.nix
|
|
|
|
|
| |
btrfs-progs was made optional in 2019 c01ea27ce356e1433da01a7b46ba40c880f2f2ac
because it didn't cross-compile. it now does
|
| |
|
| |
|
| |
|
|\
| |
| | |
nixos/systemd-boot: Add `extraEntries` and `extraFiles` options
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`mktemp` tries to use the `TMPDIR` from `nixos-install` outside of the
`chroot` instead of `/tmp` inside the `chroot` and fails. For some
reason the `TMPDIR` is being passed through the `chroot` call.
I haven't tested if other environment variables are being passed through
that shouldn't be.
|
|/
|
|
|
|
|
|
|
| |
since fc614c37c653637e5475a0b0a987489b4d1f351d nixos needs access to its
own path (<nixpkgs/nixos>) to evaluate a system with documentation.
since documentation is enabled by default almost all systems need such
access, including the installer tests. nixos-install however does not
ensure that a channel exists in the target store before evaluating the
system in that store, which can lead to `path is not valid` errors.
|
|
|
|
| |
See <https://github.com/koalaman/shellcheck/wiki/SC2086>.
|
|
|
|
| |
See <https://github.com/koalaman/shellcheck/wiki/SC2236>.
|
|
|
|
| |
See <https://github.com/koalaman/shellcheck/wiki/SC2239>.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
blaggacao/nixos-test-ref/05-class-ify-test-driver
nixos test ref/05 class ify test driver
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
This commit encapsulates the involved domain into classes and
defines explicit and typed arguments where untyped dicts where used.
It preserves backwards compatibility through legacy wrappers.
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This option can be set to disable installer tools like nixos-rebuild,
nixos-install, and nixos-generate-config (as well as more). This is
nice when a system is not expected to be rebuild or reconfigure itself
such as in a stateless PXE setup, as well as other embedded scenarios.
Note, that the system can still be updated, but it must either get
nixos-rebuild from another source, or, for embedded systems, be
upgraded by another machine like:
nix copy "$system" --to "ssh://root@<host>" && ssh "root@<host>"
"nix-env -p /nix/var/nix/profiles/system --set $system && $system/bin/switch-to-configuration switch".
Along with other options, this allows removing Perl from a closure.
For example:
{
boot.enableContainers = false;
environment.defaultPackages = [];
system.disableInstallerTools = true;
}
should not include Perl.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Changes: https://github.com/NixOS/nix/compare/2.3.12...2.3.14
Since this is a bugfix release that wasn't pushed to `nixpkgs`, I
decided to take care of it.
As it's usually done in `upload-release.pl`[1], I updated the
fallback-paths accordingly and used eval `1687468`[2] for this with Nix
2.3.14.
Also added a fallback-path for `aarch64-darwin` as Nix 2.3.14 seems to
support this now[3].
[1] https://github.com/NixOS/nix/blob/2.3-maintenance/maintainers/upload-release.pl
[2] https://hydra.nixos.org/eval/1687468
[3] https://github.com/NixOS/nix/commit/14262b86cc5825deae095c14553d623af498124c
|
| |
| |
| |
| |
| |
| | |
This adds a basic `nixos-option/default.nix` file to provide some
measure of backwards compatibility with Nixpkgs prior to
ce6f17f9530ea013d267e07d2dd958bb4e3019dd.
|
| | |
|
| |
| |
| |
| |
| |
| | |
This was done in a0a61c3e34873d02034cb804975ad2981328b5b4, but users
typically install `nixUnstable` via `nix.package`, not by overlaying
`pkgs.nix` directly.
|
| |
| |
| |
| |
| |
| | |
The patch is included in the new release, so can be dropped.
Co-authored-by: Alyssa Ross <hi@alyssa.is>
|
| |
| |
| |
| |
| |
| | |
This reverts commit 66fc303070a8ed731ffcb8733b825a03d5a2babe.
There is still a patch that doesn't apply.
|
| |
| |
| |
| | |
This reverts commit 1872bbdae55ffc82bbbe632e50fcea0e2bb5fcea.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 6f6b2cdc98f93701caf74e512ac0e3fe68730c23.
Version wasn't updated, and apparently a patch didn't apply. Let's do
this upgrade properly, in a PR, but for now I'm reverting so we don't
have a broken nix package in master.
|
| | |
|
| | |
|
| | |
|
| |
| |
| | |
fixes #25376
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since 03eaa48 added perl.withPackages, there is a canonical way to
create a perl interpreter from a list of libraries, for use in script
shebangs or generic build inputs. This method is declarative (what we
are doing is clear), produces short shebangs[1] and needs not to wrap
existing scripts.
Unfortunately there are a few exceptions that I've found:
1. Scripts that are calling perl with the -T switch. This makes perl
ignore PERL5LIB, which is what perl.withPackages is using to inform
the interpreter of the library paths.
2. Perl packages that depends on libraries in their own path. This
is not possible because perl.withPackages works at build time. The
workaround is to add `-I $out/${perl.libPrefix}` to the shebang.
In all other cases I propose to switch to perl.withPackages.
[1]: https://lwn.net/Articles/779997/
|
| |
| |
| |
| |
| | |
The desktop configuration won't enable xserver.
If there's multiple desktops enabled they will now evaluate properly.
|
| |
| |
| |
| | |
This fixes #108124.
|
|\ \
| | |
| | | |
nixos/modules: stdenv.lib -> lib
|
| | | |
|
|/ / |
|
| | |
|
|\ \
| | |
| | | |
nixos/nixos-enter: Create /tmp
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
/tmp is normally created by the systemd-tmpfiles-setup systemd service
at startup.
Fixes #39140
|
| |/
|/| |
|
| | |
|
| | |
|
| | |
|