Closed ndobbs closed 4 years ago
By default, it will try to install activesupport 6.0.0, which requires Ruby 2.5.0. This can probably be fixed by adding this line to the vagrant-serverspec.gemspec file Gem.add_runtime_dependency ‘activesupport’, ‘< 6.0.0’
The activesupport gem is actually being pulled in by rspec_html_formatter, which requests activesupport >= 4.1.4
I don’t know whey the Vagrant Ruby is trying to pull in dependency gems that aren’t compatible with it. Perhaps that would be a defect against Vagrant.
@vvchik Now that #38 is merged, would it be possible to cut a new gem to make installation easier? That would close this issue. Thanks!
Also experiencing this issue, any chance we get a new gem soon with the issue being fixed on master already?
Thanks!
I have trouble too from this issue. Do you have any temporary solution with this issue?
These workaround I use:
I wasn't able to modify the gemspec file after the install failed -- Vagrant hadn't downloaded a gem for me to modify.
Here's the end to end workaround that worked for me:
# Clone this repository locally
git clone git@github.com:vvchik/vagrant-serverspec.git
# Build the gem
cd vagrant-serverspec
gem build vagrant-serverspec.gemspec
# Install the vagrant plugin from the local gem path
# (use your own local absolute path to the gem)
vagrant plugin install /Users/becw/repos/vagrant-serverspec/vagrant-serverspec-1.3.gem
I've pushed the latest version to RubyGems. should work now, can you guys check?
I've pushed the latest version to RubyGems. should work now, can you guys check?
Hi @vvchik thanks for that.
Was it gem v1.5? It is marked as "yanked" from RubyGems
No 1.5.0, I've pushed 1.5 first, but it does not follow semver, so I decided to reupload with new version number.
@vvchik I can confirm that v1.5.0 works fine for me (vagrant 2.2.6, macos Mojave 10.14.6, Virtualbox 6.0.16).
Thanks a lot!
Solved the issue for me too
Thanks, guys for confirmation. I will close this issue then. I enabled GitHub actions so upload of new versions will happen automatically on master merge now.
Vagrant aborts the installation of this plugin due to a dependency needing a newer version of ruby,
Please let me know if I should report this bug to the vagrant team.