On Wed, Oct 31, 2012 at 08:49:34 +1100, Craig Small wrote: > 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. > Then the broken changes in 3.3.4 need to be reverted in sid ASAP.
Cheers, Julien
signature.asc
Description: Digital signature
