Comment 3 for bug 1381072

Thanks for investigating this!

This is really crappy solution from the upstream: require the newer version rather than accept the fact that the feature is broken and remove it.

Marking this as invalid for now.