| Commit message (Collapse) | Author | Age |
|---|
| |\
| |
| | |
nixos/tests/installer.nix: shorten test name to fit length limit
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
previously one of the tests would fail with
boot-after-install: starting vm
Path length (109) is longer than maximum supported length (108) and will be truncated at /nix/store/0ingn8cwwnl84i374hcl6nafsm2c5m2p-perl-5.28.0/lib/perl5/5.28.0/x86_64-linux-thread-multi/Socket.pm line 872, <__ANONIO__> line 268.
boot-after-install# qemu-system-x86_64: -monitor unix:./monitor: Failed to connect socket ./monitor: No such file or directory
error: QEMU died prematurely
QEMU died prematurely
vde_switch: EOF on stdin, cleaning up and exiting
cleaning up
builder for '/nix/store/zbpxwwxwy7f6z5z3kg4nf5mjqsywzjvx-vm-test-run-installer-filesystemEncryptedWithKeyfile.drv' failed with exit code 4
Shortening the test name fixes the issue.
|
| | |
| |
| |
| | |
fixes #33366
|
| |\ \
| |/
|/| |
netdata: 1.10.0 -> 1.11.0
|
| | |
| |
| |
| |
| |
| | |
Otherwise netdata will not find python modules.
To make sure netdata still pick up our setuid version of apps.plugin
we rename the original executable.
|
| |\ \
| | |
| | | |
nixos: move system.autoUpgrade
|
| | | |
| | |
| | |
| | | |
This is not installer-specific
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It's a quick approximation to unblock unstable channels after #48116.
This commit isn't ideal, as I suspect most wayland users won't have
xserver.enable, so they will lose the icon cache in case they had gtk
in system path (otherwise they didn't get cache anyway).
I considered using environment.noXlibs, but the nixos tests installing
headless systems do *not* get that option, so we would still be pulling
gtk in many cases where it's clearly not desired. We need to design
this more carefully.
|
| |\ \ \
| |/ /
|/| | |
nixos-generate-config: fix for swapless kernels
|
| | | |
| | |
| | |
| | | |
Fixes #49826
|
| | | | |
|
| |\ \ \
| |_|/
|/| | |
nixos/mysql: Explicitly set datadir in my.cnf
|
| | |/
| |
| |
| |
| |
| |
| | |
While this seems silly at first (it's already given as start parameter
to mysqld), it seems like xtrabackup needs that sometimes.
Without it, a Galera cluster cannot be run using the xtrabackup
replication method.
|
| |\ \
| | |
| | | |
group the release info
|
| | | |
| | |
| | |
| | |
| | | |
this makes the codename globally accessible in the repo. The release is
not only for NixOS anymore.
|
| | | |
| | |
| | |
| | | |
(cherry picked from commit e0eb712136aa8cd786955e9109afbbf8ba42555c)
|
| |\ \ \
| | | |
| | | | |
nixos/nix-daemon: default to build with all cores available
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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
|
| |/ / /
| | |
| | |
| | | |
closes #50441
|
| | | | |
|
| |/ /
| |
| |
| | |
fixes #34064
|
| |\ \
| | |
| | | |
nixos/journaldriver: import module in top-level module list
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Imports the `journaldriver` module into the top-level NixOS module
list to make it usable without extra work.
This went unnoticed in #42134 (mostly because my setup imports modules
explicitly from pinned versions).
Fixes #50390
|
| |\ \ \
| |/ /
|/| | |
gitlab: fix smtp setting
|
| | | |
| | |
| | |
| | | |
fixes #50163
|
| | | | |
|
| |\ \ \
| | | |
| | | | |
nodePackages: springclean
|
| | | | |
| | | |
| | | |
| | | | |
The package/service is broken. Upstream is dead
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | | |
Based on reports X wouldn't start out of the box and seems OK now.
In case there are still some problems, we can improve later.
I checked that nixos.tests.virtualbox.* still succeed.
|
| | | | |
| | | |
| | | |
| | | | |
... and switch to it by default in virtualbox guests
|
| |\ \ \ \
| |_|/ /
|/| | | |
Add pkgs.nixosTest
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | | |
exhibitor: fix paths for zookeeper shell scripts
|
| | | |/ /
| |/| | |
|
| |\ \ \ \
| | | | |
| | | | | |
glusterfs service: Switch to simple unit instead of forking
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Gluster's pidfile handling is bug-ridden.
I have fixed https://bugzilla.redhat.com/show_bug.cgi?id=1509340
in an attempt to improve it but that is far from enough.
The gluster developers describe another pidfile issue as
"our brick-process management is a total nightmare", see
https://github.com/gluster/glusterfs/blob/f1071f17e02502c24375c0b480d369d37f4e4054/xlators/mgmt/glusterd/src/glusterd-utils.c#L5907-L5924
I have observed multiple cases where glusterd doesn't start correctly
and systemd doesn't notice because of the erroneous pidfile handling.
To improve the situation, we don't let glusterd daemonize itself any more
and instead use `--no-daemon` and the `Simple` service type.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Docs: Add chapter on Profiles
|
| | | | | | |
| | | | | |
| | | | | | |
Co-Authored-By: DIzFer <david@izquierdofernandez.com>
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | | |
Co-Authored-By: DIzFer <david@izquierdofernandez.com>
|
| | | | | | |
| | | | | |
| | | | | | |
Co-Authored-By: DIzFer <david@izquierdofernandez.com>
|
| | | | | | |
| | | | | |
| | | | | | |
Co-Authored-By: DIzFer <david@izquierdofernandez.com>
|
| | | | | | |
| | | | | |
| | | | | | |
Co-Authored-By: DIzFer <david@izquierdofernandez.com>
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|