I noticed that mountall (and cryptsetup) depends on plymouth now. Whatever plymouth is doing or not doing, my headless system is booting fine without plymouth (dpkg --force-depends -P plymouth), yet all disks (local, NFS) are mounted and cryptsetup is setting up encrypted swap as it used to.
IMHO the "Depends: plymouth" is too hard and should be replaced with "Recommends:" or "Suggests:" for the following reasons:
- Headless systems won't ever see what plymouth is doing ("graphical boot animation")
- Plymouth itself depends on quite a few libraries (libdrm-*), unnecessarily adding code to the installation- Mountall is of "Priority: required" while plymouth is "optional". The "Depends:" makes plymouth essentially "required" as well and cannot be uninstalled w/o --force options.
Binary package hint: mountall
I noticed that mountall (and cryptsetup) depends on plymouth now. Whatever plymouth is doing or not doing, my headless system is booting fine without plymouth (dpkg --force-depends -P plymouth), yet all disks (local, NFS) are mounted and cryptsetup is setting up encrypted swap as it used to.
IMHO the "Depends: plymouth" is too hard and should be replaced with "Recommends:" or "Suggests:" for the following reasons:
- Headless systems won't ever see what plymouth is doing ("graphical boot animation")
- Plymouth itself depends on quite a few libraries (libdrm-*), unnecessarily adding code to the installation- Mountall is of "Priority: required" while plymouth is "optional". The "Depends:" makes plymouth essentially "required" as well and cannot be uninstalled w/o --force options.
Please reconsider this dependency.