Comment # 2 on bug 1050007 from Johannes Kastl

Actually, vagrant should be called and be built like any other rubygem, because
that is what the spec does. I'm trying to do that in
home:ojkastl_buildservice:Vagrant but have not finished yet and now was overrun
by the ruby 2.4 switch.

And, second thing, vagrant does explicitly need a ruby 2.2 or 2.3, but does not
work with 2.4:
https://github.com/mitchellh/vagrant/blob/master/vagrant.gemspec#L15

So, the package that is now in the mirrors should be deleted, as it won't work
without an installed ruby2.2 (which should have been deleted during zypper
dup).

I am currently working on building version 1.9.7 with ruby2.4, even if the
gemspec says it does not like 2.4.

Let's see.