Package: procps Version: 2:3.3.12-3 Severity: normal I just wasted a lot of time figuring out why my newly upgraded-to-testing failed to boot, not assembling my md raid, not detecting my lvm devices, not starting my crypted disks.
It boiled down to the udev init.d script using 'ps' to determine whether containers are supported (using a dubious test IMHO but that's beside the point). That failed due to ps not being able to run, so udev wasn't started. I've checked on another system and the ps in procps 2:3.3.9-9 doesn't try to load liblz4.so. I fail to understand why ps would need any compression... Please revert to not using libs from /usr, otherwise /bin/ps might as well move to /usr/bin/ps. -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.9-wurtel-ws (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages procps depends on: ii init-system-helpers 1.47 ii libc6 2.24-9 ii libncurses5 6.0+20161126-1 ii libncursesw5 6.0+20161126-1 ii libprocps6 2:3.3.12-3 ii libtinfo5 6.0+20161126-1 ii lsb-base 9.20161125 Versions of packages procps recommends: ii psmisc 22.21-2.1+b1 procps suggests no packages. -- no debconf information
