| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
xmrig: add meta.mainProgram
|
|
systemd-stage-1: No longer experimental
|
|
ElvishJerricco/systemd-stage-1-fix-initrd-commands
Systemd stage 1 assert initrd commands are empty
|
|
mweinelt/wyoming-openwakeword-relax-model-selection
nixos/wyoming/openwakeword: relax model selection
|
|
The wyoming-openwakeword supports a custom model directory, which cannot
be used when the the model list is constrained to the builtin ones.
|
|
nixosTests.xfce: Check if any coredumps are found
|
|
Adds a regression test for https://gitlab.xfce.org/xfce/xfconf/-/issues/35.
|
|
|
|
nixos/switch-to-configuration: Lock the switch
|
|
nixos/sslh: update and refactor for RFC42
|
|
ElvishJerricco/systemd-stage-1-bcachefs-decryption
systemd-stage-1: bcachefs decryption
|
|
chromium{Beta,Dev},google-chrome-{beta,dev}: drop
|
|
* luarocks-packages-updater: init
Goal is to make it possible to maintain out-of-tree luarocks packages
without needing to clone nixpkgs.
maintainers/scripts/update-luarocks-packages gets renamed to
pkgs/development/lua-modules/updater/updater.py
Once merged you can run for instance
nix run nixpkgs#luarocks-packages-updater -- -i contrib/luarocks-packages.csv -o contrib/generated-packages.nix
I also set the parallelism (--proc) to 1 by default else luarocks fails
because of https://github.com/luarocks/luarocks/issues/1540
* Update maintainers/scripts/pluginupdate.py
Co-authored-by: Marc Jakobi <mrcjkb89@outlook.com>
---------
Co-authored-by: Marc Jakobi <mrcjkb89@outlook.com>
|
|
Signed-off-by: Jakub Sokołowski <jakub@status.im>
|
|
When using iproute2's ip binary, you can omit the dev parameter, e.g. ip link set up eth0 instead of ip link set up dev eth0.
This breaks if for some reason your device is named e.g. he, hel, … because it is interpreted as ip link set up help.
I just encountered this bug using networking.bridges trying to create an interface named he.
I used a grep on nixpkgs to try to find iproute2 invocations using variables without the dev keyword, and found a few, and fixed them by providing the dev keyword.
I merely fixed what I found, but the use of abbreviated commands makes it a bit hard to be sure everything has been found (e.g. ip l set … up instead of ip link set … up).
|
|
systemd-stage-1: Support for user shells
|
|
|
|
|
|
|
|
This reverts commit a8f50f991948b91d1a191d1348bfff860a39b5a2.
Broke installer tests, need to figure out how to fix nixos-enter before attempting this again.
|
|
|
|
treewide: rewrite stateVersion docs (again), clean up some stateVersion usages (again)
|
|
openssh: add {Allow,Deny}{Users,Groups} settings
|
|
Match the comment in nixos-generate-config and add some more details for the curious.
|
|
Hopefully this version is clearer. Also tried to make it less technical.
|
|
|
|
From now on, we will aim to ensure that the test driver
gets tested by OfBorg using all our available tests.
This commit adds the driver timeout test to the driver.
|
|
We test that the test framework timeouts are working as expected.
|
|
For `testBuildFailure` and similar functions, we need a full blown derivation and not a lazy one.
This is an internal option for test framework developers.
|
|
Since the debut of the test-driver, we didn't obtain
a race timer with the test execution to ensure that tests doesn't run beyond
a certain amount of time.
This is particularly important when you are running into hanging tests
which cannot be detected by current facilities (requires more pvpanic wiring up, QMP
API stuff, etc.).
Two easy examples:
- Some QEMU tests may get stuck in some situation and run for more than 24 hours → we default to 1 hour max.
- Some QEMU tests may panic in the wrong place, e.g. UEFI firmware or worse → end users can set a "reasonable" amount of time
And then, we should let the retry logic retest them until they succeed and adjust
their global timeouts.
Of course, this does not help with the fact that the timeout may need to be
a function of the actual busyness of the machine running the tests.
This is only one step towards increased reliability.
|
|
systemd domainname unit - use nix store path of `net tools` for `domainname`
|
|
syslogng: Late cleanup
|
|
Rebuildable system & appliance
|
|
certspotter: init at 0.17.0; nixos/certspotter: init
|
|
needs nettools in path
|
|
nixos/unifi: fix use of optionalString
|
|
|
|
This is mainly due to the lack of maintenance in nixpkgs.
`google-chrome-{beta,dev}` depend on `chromium{Beta,Dev}`'s version
info.
`chromium{Beta,Dev}` are rarely updated and explicitly blocklisted by
`hydra.nixos.org`, meaning they are almost always outdated and not
cached in `cache.nixos.org`.
`chromium{Beta,Dev}` were intended to fix the build derivation of each
new major release (if something broke) *before* stable reached that
new major release.
Allowing for fast bumps in nixpkgs, especially if the stable bump
contains very important critical security fixes.
Something that can easily be replicated by using an early-stable release
or by manually entering a dev/beta version string in stable's
`upstream-info.nix`.
This resolves exposing end-users to outdated and vulnerable
`google-chrome-{beta,dev}` and `chromium{Beta,Dev}` versions.
|
|
ElvishJerricco/systemd-stage-1-filesystems-encrypted
systemd-stage-1: Enable more encrypted installer tests
|
|
See #246386
|
|
Signed-off-by: Christoph Heiss <christoph@c8h4.io>
|
|
|
|
pkgs is x86_64-linux, which makes the build on aarch64-linux i.e. fail.
|
|
borgmatic: fix deprecation warning check failed
|
|
|
|
|
|
|
|
|
|
Replace simple activationScripts
|
|
|
