Thanks for the heads-up Jonas. However, that wasn't the right call. I cc'ed you just to let you know that you were being mentioned in this discussion (and to let you know that I would be working on a patch for a bug that I hadn't opened yet!), but this bug was not blocked by any other bug present in the BTS at the time of writing that answer. Bug#1089204, which you tagged as being a blocker, is actually not since technically it was closed by disabling the --no-default-features tests (even if the fix could be improved, as we said). In the meantime, plugwash filed #1089917 with a patch, which is indeed a suitable blocker for this one.
P.S.: It was matter of minutes, I was just finishing working on the same patch as plugwash and then open the bug and add the blocker.
