Okay, I think this is totally our fault! So sorry!
We've uploaded a patch for the patch, and this bug should be fixed.
