search

wafflesfm / batter

It makes Waffles.
Other
83 stars 18 forks source link

undefined method `configure' for Vagrant:Module (NoMethodError) #1

Closed edgewyn closed 11 years ago

edgewyn commented 11 years ago

I'm getting this error on the current develop branch (19d92600213bf2d690c69d93b3c17ff7dfda3f99). Vagrant is installed properly and works on vagrantfiles from other projects.

➜ vagrant git:(develop) vagrant up /home/user/projects/batter/vagrant/Vagrantfile:4:in <top (required)>': undefined methodconfigure' for Vagrant:Module (NoMethodError) from /home/user/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/config/loader.rb:115:in load' from /home/user/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/config/loader.rb:115:inblock in procs_for_source' from /home/user/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/config.rb:41:in block in capture_configures' from <internal:prelude>:10:insynchronize' from /home/user/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/config.rb:36:in capture_configures' from /home/user/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/config/loader.rb:114:inprocs_for_source' from /home/user/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/config/loader.rb:51:in block in set' from /home/user/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/config/loader.rb:45:ineach' from /home/user/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/config/loader.rb:45:in set' from /home/user/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:377:inblock in load_config!' from /home/user/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:392:in call' from /home/user/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:392:inload_config!' from /home/user/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/lib/vagrant/environment.rb:327:in load!' from /home/user/.rbenv/versions/1.9.3-p385/lib/ruby/gems/1.9.1/gems/vagrant-1.0.6/bin/vagrant:40:in<top (required)>' from /home/user/.rbenv/versions/1.9.3-p385/bin/vagrant:23:in load' from /home/user/.rbenv/versions/1.9.3-p385/bin/vagrant:23:in

'

Ell commented 11 years ago

What version of vagrant are you running?

EDIT: 1.0.6

I had the same issue and updating vagrant fixed it. We're using some stuff that was implemented in the 1.1.x release of vagrant

edgewyn commented 11 years ago

Yep, 1.0.6. I updated, but only to 1.0.7 - it doesn't look like rubygems is hosting anything on the 1.1.x series. I can't use the Vagrant-provided install file because I use rbenv to manage ruby/gems and the Vagrant-provided file installs to a nonstandard location.

Is there any chance we could avoid using the 1.1.x stuff, at least until rubygems hosts the 1.1.x release?

edgewyn commented 11 years ago

It turns out there isn't going to be a 1.1.x release of rubygems, so I just uninstalled the rbenv gem, rm'ed ~/bin/vagrant, and installed the binary version from vagrantup.com.