Yep, I'm on it. I don't know how to tag this: it's not failing, it's just working on 1.9 while it should be 2.0 only. An idea would be to just leave `ruby_version_is "2.0"` and ignore the fact that on Rubinius it also works on 1.9. As you said, we'll move to 2.x only soon, so it wouldn't be a problem for the future. What do you think?