Using regular Vagrant after working on a plugin...

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Using regular Vagrant after working on a plugin...

VMTrooper
Hello Everyone,

I tried hacking around with the vagrant-rackspace plugin.  When I was ready to resume running Vagrant regularly, I kept getting path errors like the following:

/Users/vmtrooper/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:298:in `to_specs': Could not find 'vagrant' (>= 0) among 46 total gem(s) (Gem::LoadError)
from /Users/vmtrooper/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:309:in `to_spec'
from /Users/vmtrooper/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_gem.rb:47:in `gem'
from /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin/vagrant:22:in `<main>'
from /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin/ruby_executable_hooks:15:in `eval'
from /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin/ruby_executable_hooks:15:in `<main>'

I resolved the issue by renaming the vagrant binary at /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin.  However, I'd like to know what is the proper way to resume using regular Vagrant after working on a plugin?

I'm a Linux novice.  So, I'm sure there is an obvious answer that I'm just not getting.

Thanks for any help you can provide,
Trevor


--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Using regular Vagrant after working on a plugin...

Samuel Brown
I would like to see the answer to this as well, just ran into this issue today and I was a little confused.

Big thanks to Trevor for posting his fix so that I could move on!

-Sam

On Saturday, December 28, 2013 6:35:39 PM UTC-5, Trevor Roberts wrote:
Hello Everyone,

I tried hacking around with the vagrant-rackspace plugin.  When I was ready to resume running Vagrant regularly, I kept getting path errors like the following:

/Users/vmtrooper/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:298:in `to_specs': Could not find 'vagrant' (>= 0) among 46 total gem(s) (Gem::LoadError)
from /Users/vmtrooper/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:309:in `to_spec'
from /Users/vmtrooper/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_gem.rb:47:in `gem'
from /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin/vagrant:22:in `<main>'
from /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin/ruby_executable_hooks:15:in `eval'
from /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin/ruby_executable_hooks:15:in `<main>'

I resolved the issue by renaming the vagrant binary at /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin.  However, I'd like to know what is the proper way to resume using regular Vagrant after working on a plugin?

I'm a Linux novice.  So, I'm sure there is an obvious answer that I'm just not getting.

Thanks for any help you can provide,
Trevor


--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Using regular Vagrant after working on a plugin...

Ringo De Smet
In reply to this post by VMTrooper
Did you use an RVM gemset specifically for your plugin hacking? Using another Ruby and/or gemset would solve your problem.

Ringo

On Sunday, 29 December 2013 00:35:39 UTC+1, Trevor Roberts wrote:
Hello Everyone,

I tried hacking around with the vagrant-rackspace plugin.  When I was ready to resume running Vagrant regularly, I kept getting path errors like the following:

/Users/vmtrooper/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:298:in `to_specs': Could not find 'vagrant' (>= 0) among 46 total gem(s) (Gem::LoadError)
from /Users/vmtrooper/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:309:in `to_spec'
from /Users/vmtrooper/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_gem.rb:47:in `gem'
from /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin/vagrant:22:in `<main>'
from /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin/ruby_executable_hooks:15:in `eval'
from /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin/ruby_executable_hooks:15:in `<main>'

I resolved the issue by renaming the vagrant binary at /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin.  However, I'd like to know what is the proper way to resume using regular Vagrant after working on a plugin?

I'm a Linux novice.  So, I'm sure there is an obvious answer that I'm just not getting.

Thanks for any help you can provide,
Trevor


--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Using regular Vagrant after working on a plugin...

VMTrooper
Hello Ringo,

I used RVM to change to an updated Ruby (1.9.3, i believe).  I recently updated to Mavericks, which includes Ruby 2.x.  I will see if the behavior still persists.

Just to be clear, the standard workflow is to use RVM to switch to a specific Ruby version for working with plugins.  Then, when your done, switch back to your "production" Ruby for normal operations?

Thanks,
Trevor



On Wed, Jan 15, 2014 at 8:20 AM, Ringo De Smet <[hidden email]> wrote:
Did you use an RVM gemset specifically for your plugin hacking? Using another Ruby and/or gemset would solve your problem.

Ringo


On Sunday, 29 December 2013 00:35:39 UTC+1, Trevor Roberts wrote:
Hello Everyone,

I tried hacking around with the vagrant-rackspace plugin.  When I was ready to resume running Vagrant regularly, I kept getting path errors like the following:

/Users/vmtrooper/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:298:in `to_specs': Could not find 'vagrant' (>= 0) among 46 total gem(s) (Gem::LoadError)
from /Users/vmtrooper/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:309:in `to_spec'
from /Users/vmtrooper/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_gem.rb:47:in `gem'
from /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin/vagrant:22:in `<main>'
from /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin/ruby_executable_hooks:15:in `eval'
from /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin/ruby_executable_hooks:15:in `<main>'

I resolved the issue by renaming the vagrant binary at /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin.  However, I'd like to know what is the proper way to resume using regular Vagrant after working on a plugin?

I'm a Linux novice.  So, I'm sure there is an obvious answer that I'm just not getting.

Thanks for any help you can provide,
Trevor


--
You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/gcw3LLNVYao/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Using regular Vagrant after working on a plugin...

Ringo De Smet


On Wednesday, 15 January 2014 17:27:36 UTC+1, Trevor Roberts wrote:
Hello Ringo,

I used RVM to change to an updated Ruby (1.9.3, i believe).  I recently updated to Mavericks, which includes Ruby 2.x.  I will see if the behavior still persists.

Just to be clear, the standard workflow is to use RVM to switch to a specific Ruby version for working with plugins.  Then, when your done, switch back to your "production" Ruby for normal operations?

For every Ruby development project (e.g a Vagrant plugin), I use a specific Ruby *with* a specific gemset. I suggest you read up about gemset basics:

http://rvm.io/gemsets/basics

Ringo

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
Reply | Threaded
Open this post in threaded view
|

Re: Using regular Vagrant after working on a plugin...

Bill WANG
In reply to this post by VMTrooper
I got exact same error, but the way to rename bin folder didn't fix my issue.

Waste a lot of time on it , and finally fixed it by myself. Don't know why it fixed by this way, put here for a workaround.

gem install vagrant
gem uninstall vagrant

Regards,
Bill

On Sunday, December 29, 2013 10:35:39 AM UTC+11, Trevor Roberts Jr wrote:
Hello Everyone,

I tried hacking around with the vagrant-rackspace plugin.  When I was ready to resume running Vagrant regularly, I kept getting path errors like the following:

/Users/vmtrooper/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:298:in `to_specs': Could not find 'vagrant' (>= 0) among 46 total gem(s) (Gem::LoadError)
from /Users/vmtrooper/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:309:in `to_spec'
from /Users/vmtrooper/.rvm/rubies/ruby-1.9.3-p484/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_gem.rb:47:in `gem'
from /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin/vagrant:22:in `<main>'
from /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin/ruby_executable_hooks:15:in `eval'
from /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin/ruby_executable_hooks:15:in `<main>'

I resolved the issue by renaming the vagrant binary at /Users/vmtrooper/.rvm/gems/ruby-1.9.3-p484/bin.  However, I'd like to know what is the proper way to resume using regular Vagrant after working on a plugin?

I'm a Linux novice.  So, I'm sure there is an obvious answer that I'm just not getting.

Thanks for any help you can provide,
Trevor


--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.