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

RuntimeError: vagrant-share can't be installed without vagrant-login #5050

Closed
ngdinhtoan opened this Issue Dec 22, 2014 · 5 comments

Comments

Projects
None yet
5 participants
@ngdinhtoan
Copy link

ngdinhtoan commented Dec 22, 2014

Acctually, this error appear when I type some incorrect command.

$ vagrant help
/opt/vagrant/embedded/gems/gems/vagrant-share-1.1.2/lib/vagrant-share/activate.rb:8:in `rescue in <encoded>': vagrant-share can't be installed without vagrant-login (RuntimeError)
    from /opt/vagrant/embedded/gems/gems/vagrant-share-1.1.2/lib/vagrant-share/activate.rb:5:in `<encoded>'
    from /opt/vagrant/embedded/gems/gems/vagrant-share-1.1.2/lib/vagrant-share/activate.rb:16:in `RGLoader_load'
    from /opt/vagrant/embedded/gems/gems/vagrant-share-1.1.2/lib/vagrant-share/activate.rb:16:in `<top (required)>'
    from /opt/vagrant/embedded/gems/gems/vagrant-share-1.1.2/lib/vagrant-share.rb:23:in `require'
    from /opt/vagrant/embedded/gems/gems/vagrant-share-1.1.2/lib/vagrant-share.rb:23:in `block in <class:Plugin>'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/cli.rb:75:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/cli.rb:75:in `block (2 levels) in help'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/registry.rb:48:in `block in each'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/registry.rb:47:in `each'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/registry.rb:47:in `each'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/cli.rb:69:in `block in help'
    from /opt/vagrant/embedded/lib/ruby/2.0.0/optparse.rb:885:in `initialize'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/cli.rb:57:in `new'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/cli.rb:57:in `help'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/cli.rb:32:in `execute'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/environment.rb:301:in `cli'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/plugins/commands/help/command.rb:11:in `execute'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/cli.rb:42:in `execute'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.7.0/lib/vagrant/environment.rb:301:in `cli'
    from /opt/vagrant/bin/../embedded/gems/gems/vagrant-1.7.0/bin/vagrant:174:in `<main>'

I think it should not output like this.

@sethvargo

This comment has been minimized.

Copy link
Contributor

sethvargo commented Dec 22, 2014

This has been fixed in the latest version of Vagrant. Please install the latest version of Vagrant from vagrantup.com.

@sethvargo sethvargo closed this Dec 22, 2014

@lonniev

This comment has been minimized.

Copy link
Contributor

lonniev commented Jan 19, 2015

Nicely understated @ngdinhtoan. You are right: foobarring a utility's little help message is not something desirable. ;-)

It's an effective way to force users to update, though!

@ngdinhtoan

This comment has been minimized.

Copy link
Author

ngdinhtoan commented Jan 20, 2015

Upgraded :)

On Mon, Jan 19, 2015, 20:52 Lonnie VanZandt notifications@github.com
wrote:

Nicely understated @ngdinhtoan https://github.com/ngdinhtoan. You are
right: foobarring a utility's little help message is not something
desirable. ;-)

It's an effective way to force users to update, though!


Reply to this email directly or view it on GitHub
#5050 (comment).

@awalls

This comment has been minimized.

Copy link

awalls commented Feb 4, 2015

Was getting this error on 1.6.5. Upgraded to latest version 1.7.2 which appears to have fixed the problem.

@exuperok

This comment has been minimized.

Copy link

exuperok commented Feb 18, 2015

fixed forme as well after upgrading to 1.7.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.