Control: found -1 2:3.3.12-2 On 2016-11-26 09:44:44 +1300, Ben Caradoc-Davies wrote: > I think that this bug affects only systems that have /usr on a separate > filesystem. > > I upgraded procps on a system in which /usr is on the root filesystem and > encountered no problems at boot time. > > Please consider adjusting the title of this report for the benefit of your > apt-listbugs readers because critical bugs cause apt-get upgrade to prompt > for user input.
In any case, nothing has changed in procps, i.e. with procps 2:3.3.12-2, I get: $ ldd =ps linux-vdso.so.1 (0x00007ffea6b6e000) libgtk3-nocsd.so.0 => /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 (0x00007fc3129f1000) libprocps.so.6 => /lib/x86_64-linux-gnu/libprocps.so.6 (0x00007fc3127cd000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fc3125c9000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fc31222b000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fc31200e000) libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007fc311f82000) ^^^^^^^^^^^^^^^ /lib64/ld-linux-x86-64.so.2 (0x000055e95d899000) libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007fc311d5a000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fc311b52000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007fc31192c000) liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x00007fc31171a000) libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007fc31140b000) libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fc311196000) libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007fc310f82000) So, marking as found in 2:3.3.12-2 so that apt-listbugs doesn't complain in the upgrade. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)