Bug#692074: unblock: procps/1:3.3.5-1

2012-11-04 Thread Craig Small
On Thu, Nov 01, 2012 at 08:10:55PM -0700, Jonathan Nieder wrote: > 1. prepare 3.3.4-2 backing out the ABI change, > ask ftpmasters to reject 3.3.5-1 from NEW I emailled them tonight. > 2. upload 3.3.4-2 Uploaded a few minutes ago > 3. coordinate with the release team on the next step (prob

Bug#692074: unblock: procps/1:3.3.5-1

2012-11-01 Thread Jonathan Nieder
Craig Small wrote: > Tell me how to do it (not the API change, but more around the what > version etc) and I will. > > I assume its making a 3.3.4-2 with a debian patch to reverse the API > and then do.. something. I think the steps are: 1. prepare 3.3.4-2 backing out the ABI change, ask ft

Bug#692074: unblock: procps/1:3.3.5-1

2012-11-01 Thread Craig Small
On Thu, Nov 01, 2012 at 05:37:37PM -0700, Jonathan Nieder wrote: > I think including libprocps1 in wheezy would be good, but would it be > possible to back out the ABI break in sid in the meantime? Tell me how to do it (not the API change, but more around the what version etc) and I will. I assume

Bug#692074: unblock: procps/1:3.3.5-1

2012-11-01 Thread Jonathan Nieder
Craig Small wrote: > Please unblock package procps If I understand correctly this involves a small transition: $ cupt rdepends libprocps0 Reverse-Depends: libprocps0-dev 1:3.3.4-1: libprocps0 (= 1:3.3.4-1) Reverse-Depends: open-vm-tools 2:8.8.0+2012.05.21-724730-1+nmu1: libprocps0 (>= 1:3.

Bug#692074: unblock: procps/1:3.3.5-1

2012-11-01 Thread Craig Small
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package procps procps 3.3.5-1 is blocked because libproc1 is new. The problem is that the oldest libproc0 will not work with 3.3.5-1 because the API changed. This means curr