Hi, I'm trying to make sure procps 3.3.4-1 is not going to be progressed along any further. The API changed which means if procps is upgraded and libproc0 isn't, then some procps commands don't work well. I've reported a critical bug [1] on procps (it stops the boot process) but 3.3.5 is stuck because the package name has changed to libproc1. Ideally I'd like 3.3.4 gone but I think its too late for that, so some things depending on libproc0 may go strange. - Craig [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691847 -- Craig Small VK2XLZ http://enc.com.au/ csmall at : enc.com.au Debian GNU/Linux http://www.debian.org/ csmall at : debian.org GPG fingerprint: 5D2F B320 B825 D939 04D2 0519 3938 F96B DF50 FEA5
Attachment:
signature.asc
Description: Digital signature