are you running this from a path with a Vagrantfile?
and try do commands from a clean directory without any Vagrantfile to check if the error still happen. If you are ok deleting all, delete also ~/.vagrant.d On Fri, May 23, 2014 at 8:42 AM, mechastorm_w <[email protected]>wrote: > I am having an issue in running Vagrant after I upgraded it to 1.6.2. > > I am currently on Ubuntu Desktop 14.04 and was previously running Vagrant > 1.3.5 > > What I had done > > - Remove the old vagrant installation (deleted the /opt/vagrant > directory and the /usr/bin/vagrant file) > - Downloaded and installed the 64-bit debian package for Vagrant 1.6.2 > - Ran vagrant -v , which showed 1.6.2 > - Any other vagrant command like vagrant up or even vagrant init give > me this error > > /opt/vagrant/embedded/gems/gems/bundler-1.6.2/lib/bundler/dsl.rb:92:in >> `gem': You cannot specify the same gem twice with different version >> requirements. (Bundler::GemfileError) >> You specified: vagrant (= 1.6.2) and vagrant (>= 0) >> from /tmp/vagrant20140522-3680-15g89rn2:7:in `block in eval_gemfile' >> from >> /opt/vagrant/embedded/gems/gems/bundler-1.6.2/lib/bundler/dsl.rb:183:in >> `group' >> from /tmp/vagrant20140522-3680-15g89rn2:4:in `eval_gemfile' >> from >> /opt/vagrant/embedded/gems/gems/bundler-1.6.2/lib/bundler/dsl.rb:36:in >> `instance_eval' >> from >> /opt/vagrant/embedded/gems/gems/bundler-1.6.2/lib/bundler/dsl.rb:36:in >> `eval_gemfile' >> from >> /opt/vagrant/embedded/gems/gems/bundler-1.6.2/lib/bundler/dsl.rb:10:in >> `evaluate' >> from >> /opt/vagrant/embedded/gems/gems/bundler-1.6.2/lib/bundler/definition.rb:26:in >> `build' >> from /opt/vagrant/embedded/gems/gems/bundler-1.6.2/lib/bundler.rb:153:in >> `definition' >> from /opt/vagrant/embedded/gems/gems/bundler-1.6.2/lib/bundler.rb:116:in >> `setup' >> from >> /opt/vagrant/bin/../embedded/gems/gems/vagrant-1.6.2/bin/vagrant:71:in >> `<main>' > > > Google so far has turned up nothing for me unless I was serching for the > wrong term. Anyone has an idea of what I can do to move forward with this - > right now this is stopping from using vagrant as a whole. > > Invoke Labs – Business Catalyst > Twitter <http://www.twitter.com/InvokeLabs> | > Facebook<http://www.facebook.com/InvokeLabs> > | LinkedIn <http://www.linkedin.com/company/invoke-labs> | > Blog<http://invokelabs.com/blog> > > *Check out the newest member of our Collective, Cleanify > <http://www.cleanify.com>, see our upcoming University of Invoke workshops > <http://www.eventbrite.ca/o/invoke-labs-5892948895>, and join us in the > woods for the inaugural Community Manager CampAway > <http://campaway.invokelabs.com/cm2014>. * > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
