Package: initramfs-tools-core Version: 0.137 Severity: normal X-Debbugs-Cc: die...@gnome.org
cryptsetup expects the `/run/cryptsetup` directory to exist, and according to upstream the preferred way to get it to exist is with a tmpfiles.d file: https://gitlab.com/cryptsetup/cryptsetup/-/merge_requests/99#note_390506222 `initramfs-core-tools` however just creates it manually: ``` /usr/share/initramfs-tools /scripts/local-top/cryptroot: # Create locking directory before invoking cryptsetup(8) to avoid warnings mkdir -pm0700 /run/cryptsetup ``` `dracut` does something similar in its scripts, but apparently in my system systemd takes over and said script is never run, or ran too late? ``` /usr/lib/dracut/modules.d/90crypt/cryptroot-ask.sh: mkdir -p -m 0700 /run/cryptsetup ``` So, I believe perhaps the above directory might follow upstream recommendation and be created in a tmpfiles.d configuration file. Note that /usr/lib/tmpfiles.d/cryptsetup.conf is installed by `cryptsetup-bin`. A similar bug was opened for `dracut`: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967921 -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages initramfs-tools-core depends on: ii coreutils 8.32-2 ii cpio 2.13+dfsg-2 ii e2fsprogs 1.45.6-1 ii klibc-utils 2.0.7-1 ii kmod 27+20200310-2 ii logsave 1.45.6-1 ii udev 246-2 Versions of packages initramfs-tools-core recommends: ii busybox 1:1.30.1-4 ii pigz 2.4-1+b1 Versions of packages initramfs-tools-core suggests: ii bash-completion 1:2.10-1 -- Configuration Files: /etc/initramfs-tools/initramfs.conf changed [not included] -- no debconf information
