d9b1bde390
Version 251.6 of systemd introduced a small change[1] that now checks whether the fsck command is available in *addition* to the filesystem specific fsck.$fsname executable. When bumping systemd to version 251.7 on our side[2], we introduced that change. This subsequently caused our "fsck" test to fail and it looks like this was an oversight during the pull request[3] introducing the bump. Since the fsck wrapper binary is in util-linux, I decided to address this by adding util-linux to fsPackages because util-linux is already part of the closure of any NixOS system so the impact should be pretty low. [1]: |
||
|---|---|---|
| .. | ||
| filesystems | ||
| auto-upgrade.nix | ||
| bcache.nix | ||
| cpu-freq.nix | ||
| encrypted-devices.nix | ||
| filesystems.nix | ||
| lvm.nix | ||
| network-interfaces-scripted.nix | ||
| network-interfaces-systemd.nix | ||
| network-interfaces.nix | ||
| powertop.nix | ||
| scsi-link-power-management.nix | ||
| snapraid.nix | ||
| stratis.nix | ||
| swraid.nix | ||
| trackpoint.nix | ||
| tty-backgrounds-combine.sh | ||