Hi, On Thu, Apr 20, 2017 at 03:45:29AM -0500, Michael Lustfield wrote: > Here we go... > > The packer failure seems very unsurprising and I expect it to be an easy one > to > deal with. Every other reverse build dependency that ratt detected built > without failure.
So we could try to see if we can get the fix into testing. The first issue is that golang-go.crypto contains a lot of unrelated changes in unstable, which (probably) aren't suitable for an unblock. So these need to be reverted. So you need to upload a version of golang-go.crypto which is based on the version in testing, with the patch for CVE-2017-3204 on top. After that, the rdeps need to be rebuilt and fixed (if necessary). If your tests are any indication, that shouldn't be a big issue. When all the rdeps are ok, the whole group of rebuilt/fixed packages can go into testing. That way we can avoid having to remove the old unfixed ones. Cheers, Ivo
