Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

installing vagrant-scp gives NoMethodError #7761

Closed
saisandeep opened this issue Aug 27, 2016 · 4 comments
Closed

installing vagrant-scp gives NoMethodError #7761

saisandeep opened this issue Aug 27, 2016 · 4 comments
Milestone

Comments

@saisandeep
Copy link

Please note that the Vagrant issue tracker is reserved for bug reports and
enhancements. For general usage questions, please use the Vagrant mailing list:
https://groups.google.com/forum/#!forum/vagrant-up. Thank you!

Vagrant version

Vagrant 1.8.5

Host operating system

OSX el capitan

Guest operating system

ubuntu-trusty tahr

Vagrantfile

Vagrant.configure("2") do |config|
    config.vm.box = "ubuntu1"
end

Please note, if you are using Homestead or a different Vagrantfile format, we
may be unable to assist with your issue. Try to reproduce the issue using a
vanilla Vagrantfile first.

Debug output

Provide a link to a GitHub Gist containing the complete debug output:
https://www.vagrantup.com/docs/other/debugging.html. The debug output should
be very long. Do NOT paste the debug output in the issue, just paste the
link to the Gist.

Expected behavior

Successful installation of vagrant-scp

Actual behavior

got an /opt/vagrant/embedded/gems/gems/bundler-1.12.5/lib/bundler/resolver.rb:202:in map': undefined methodto_specs' for nil:NilClass (NoMethodError)

Steps to reproduce

  1. Install vagrant 1.8.5
  2. vagrant plugin install vagrant-scp

References

Are there any other GitHub issues (open or closed) that should be linked here?
For example:

@saisandeep
Copy link
Author

saisandeep commented Aug 27, 2016

This is what I was getting when trying to install vagrant plugin, the bundler seems to of version 1.12.5

$ vagrant plugin install vagrant-scp Installing the 'vagrant-scp' plugin. This can take a few minutes... /opt/vagrant/embedded/gems/gems/bundler-1.12.5/lib/bundler/resolver.rb:202:in 'map': undefined method 'to_specs' for nil:NilClass (NoMethodError) from /opt/vagrant/embedded/gems/gems/bundler-1.12.5/lib/bundler/resolver.rb:202:in 'start' from /opt/vagrant/embedded/gems/gems/bundler-1.12.5/lib/bundler/resolver.rb:184:in 'resolve' from /opt/vagrant/embedded/gems/gems/bundler-1.12.5/lib/bundler/definition.rb:200:in 'resolve' from /opt/vagrant/embedded/gems/gems/bundler-1.12.5/lib/bundler/definition.rb:140:in 'specs' from /opt/vagrant/embedded/gems/gems/bundler-1.12.5/lib/bundler/definition.rb:129:in 'resolve_remotely!' from /opt/vagrant/embedded/gems/gems/bundler-1.12.5/lib/bundler/installer.rb:195:in 'resolve_if_need' from /opt/vagrant/embedded/gems/gems/bundler-1.12.5/lib/bundler/installer.rb:70:in 'run' from /opt/vagrant/embedded/gems/gems/bundler-1.12.5/lib/bundler/installer.rb:22:in 'install' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/bundler.rb:230:in 'block in internal_install' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/bundler.rb:294:in 'block in with_isolated_gem' from /opt/vagrant/embedded/lib/ruby/2.2.0/rubygems/user_interaction.rb:45:in 'use_ui' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/bundler.rb:293:in 'with_isolated_gem' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/bundler.rb:229:in 'internal_install' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/bundler.rb:102:in 'install' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/plugin/manager.rb:62:in 'block in install_plugin' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/plugin/manager.rb:72:in 'call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/plugin/manager.rb:72:in 'install_plugin' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/commands/plugin/action/install_gem.rb:37:in 'call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/warden.rb:34:in 'call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/builder.rb:116:in 'call' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in 'block in run' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/util/busy.rb:19:in 'busy' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/action/runner.rb:66:in 'run' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/commands/plugin/command/base.rb:14:in 'action' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/commands/plugin/command/install.rb:32:in 'block in execute' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/commands/plugin/command/install.rb:31:in 'each' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/commands/plugin/command/install.rb:31:in 'execute' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/plugins/commands/plugin/command/root.rb:56:in 'execute' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/cli.rb:42:in 'execute' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/lib/vagrant/environment.rb:302:in 'cli' from /opt/vagrant/embedded/gems/gems/vagrant-1.8.5/bin/vagrant:174:in '<main>'

@thomdixon
Copy link

👍 Had to revert back to 1.8.0 to get it working.

@chrisroberts chrisroberts added this to the 1.8 milestone Oct 4, 2016
@chrisroberts
Copy link
Member

Hi there,

It looks like this has been resolved within a previously shipped version of Vagrant so I am now closing this issue. If the original issue was not fully resolved, please reopen this issue or create a new one.

Cheers!

@ghost
Copy link

ghost commented Apr 2, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants