···
# Regression test for systemd-timesync having moved the state directory without
# upstream providing a migration path. https://github.com/systemd/systemd/issues/12131
4
-
import ./make-test.nix (let
4
+
import ./make-test-python.nix (let
# override the `false` value from the qemu-vm base profile
services.timesyncd.enable = lib.mkForce true;
···
29
-
$current->succeed('systemctl status systemd-timesyncd.service');
29
+
current.succeed("systemctl status systemd-timesyncd.service")
# on a new install with a recent systemd there should not be any
# leftovers from the dynamic user mess
32
-
$current->succeed('test -e /var/lib/systemd/timesync');
33
-
$current->succeed('test ! -L /var/lib/systemd/timesync');
32
+
current.succeed("test -e /var/lib/systemd/timesync")
33
+
current.succeed("test ! -L /var/lib/systemd/timesync")
# timesyncd should be running on the upgrading system since we fixed the
# file bits in the activation script
37
-
$pre1909->succeed('systemctl status systemd-timesyncd.service');
37
+
pre1909.succeed("systemctl status systemd-timesyncd.service")
# the path should be gone after the migration
40
-
$pre1909->succeed('test ! -e /var/lib/private/systemd/timesync');
40
+
pre1909.succeed("test ! -e /var/lib/private/systemd/timesync")
# and the new path should no longer be a symlink
43
-
$pre1909->succeed('test -e /var/lib/systemd/timesync');
44
-
$pre1909->succeed('test ! -L /var/lib/systemd/timesync');
43
+
pre1909.succeed("test -e /var/lib/systemd/timesync")
44
+
pre1909.succeed("test ! -L /var/lib/systemd/timesync")
# after a restart things should still work and not fail in the activation
# scripts and cause the boot to fail..
50
-
$pre1909->succeed('systemctl status systemd-timesyncd.service');
50
+
pre1909.succeed("systemctl status systemd-timesyncd.service")