[vagrant-up] Re: Vagrant-aws Plugin Installation Fails (Windows) - Could not find 'fog-xml'

2016-12-01 Thread croberts 
Hi Leonid,

It looks like the generated solution set for installation can end up with 
some specs out of order causing this error during validation but prior to 
installation. I have the fixed staged in a PR and it will be within the 
next release:

https://github.com/mitchellh/vagrant/pull/8068

Cheers!

On Thursday, December 1, 2016 at 6:19:46 AM UTC-8, Leonid Belkind wrote:
>
> Guys,
>
> I am new to Vagrant, trying to use it to automate creation and 
> configuration of AWS Instances.
> Installed Version: 1.9.0
> Trying to install vagrant-aws plugin, I am getting the following:
>
> Installing the 'vagrant-aws' plugin. This can take a few minutes...
> C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/dependency.rb:315:in 
> `to_specs': Could not find 'fog-xml' (>= 0) among 45 total gem(s) 
> (Gem::LoadError)
> Checked in 'GEM_PATH=C:/HashiCorp/Vagrant/embedded/gems', execute `gem 
> env` for more information
> from 
> C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:1311:in
>  
> `block in activate_dependencies'
> from 
> C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:1300:in
>  
> `each'
> from 
> C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:1300:in
>  
> `activate_dependencies'
> from 
> C:/HashiCorp/Vagrant/embedded/lib/ruby/2.2.0/rubygems/specification.rb:1282:in
>  
> `activate'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/bundler.rb:319:in
>  
> `block in activate_solution'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/bundler.rb:316:in
>  
> `each'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/bundler.rb:316:in
>  
> `activate_solution'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/bundler.rb:244:in
>  
> `internal_install'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/bundler.rb:97:in
>  
> `install'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/plugin/manager.rb:62:in
>  
> `block in install_plugin'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/plugin/manager.rb:72:in
>  
> `call'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/plugin/manager.rb:72:in
>  
> `install_plugin'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/plugins/commands/plugin/action/install_gem.rb:37:in
>  
> `call'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/warden.rb:34:in
>  
> `call'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/builder.rb:116:in
>  
> `call'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/runner.rb:66:in
>  
> `block in run'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/util/busy.rb:19:in
>  
> `busy'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/action/runner.rb:66:in
>  
> `run'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/plugins/commands/plugin/command/base.rb:14:in
>  
> `action'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/plugins/commands/plugin/command/install.rb:32:in
>  
> `block in execute'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/plugins/commands/plugin/command/install.rb:31:in
>  
> `each'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/plugins/commands/plugin/command/install.rb:31:in
>  
> `execute'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/plugins/commands/plugin/command/root.rb:66:in
>  
> `execute'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/cli.rb:42:in
>  
> `execute'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/lib/vagrant/environment.rb:308:in
>  
> `cli'
> from 
> C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.9.0/bin/vagrant:123:in 
> `'
>
> Indeed, when looking in the vagrant/embedded/gems, the gem named fog-xml 
> is missing.
> Any ideas?
>
> Thanks in advance
> Leonid
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit

[vagrant-up] Re: fusion plugin not working with uninitialized constant Vagrant (NameError)

2016-11-29 Thread croberts 
Please try uninstalling the plugin, and installing again. It should resolve 
the issue.

On Monday, November 28, 2016 at 2:47:07 PM UTC-8, Simon Green wrote:
>
> Hi,
>
> I've just bought the Fusion plugin and it's not working for me.
>
> Running:
>
> vagrant init geerlingguy/ubuntu1404; vagrant up --provider vmware_fusion
>
> Errors with:
>
> /Users/simon/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.15/bin/
> vagrant_vmware_desktop_sudo_helper:16:in `': uninitialized 
> constant Vagrant (NameError)
>  from 
> /Users/simon/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.15/bin/vagrant_vmware_desktop_sudo_helper:44:in
>  
> `RGLoader_load'
>  from 
> /Users/simon/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.15/bin/vagrant_vmware_desktop_sudo_helper:44:in
>  
> `'
>
>
> Fresh installation of VMWare Fusion 8.5.2 and Vagrant 1.8.7
>
> Here is the --debug output immediately following the curl to check the box 
> is up to date:
>
>  INFO warden: Calling IN action: 
> #
>  INFO runner: Preparing hooks for middleware sequence...
>  INFO runner: 1 hooks defined.
>  INFO runner: Running action: machine_action_up 
> #
>  INFO warden: Calling IN action: VMware Middleware: Running
>  INFO subprocess: Starting process: ["/Applications/VMware 
> Fusion.app/Contents/Library/vmrun", "list"]
> DEBUG subprocess: Command not in installer, not touching env vars.
>  INFO subprocess: Command not in installer, restoring original environment
> ...
> DEBUG subprocess: Selecting on IO
> DEBUG subprocess: stdout: Total running VMs: 0
> DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
> DEBUG subprocess: Exit status: 0
> DEBUG vmware: VM state requested. Current state: not_running
>  INFO warden: Calling OUT action: VMware Middleware: Running
>  INFO runner: Preparing hooks for middleware sequence...
>  INFO runner: 1 hooks defined.
>  INFO runner: Running action: machine_action_up 
> #
>  INFO warden: Calling IN action: 
> #  
> (lambda)>
>  INFO warden: Calling IN action: VMware Middleware: PruneForwardedPorts
>  INFO prune_forwarded_ports: Pruning forwarded ports...
> DEBUG environment: Attempting to acquire process-lock: vmware-network
> DEBUG environment: Attempting to acquire process-lock: dotlock
>  INFO environment: Acquired process lock: dotlock
>  INFO environment: Released process lock: dotlock
>  INFO environment: Acquired process lock: vmware-network
>  INFO subprocess: Starting process: [
> "/Users/simon/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.15/bin/vagrant_vmware_desktop_sudo_helper_wrapper_darwin_amd64"
> , "prune-forwarded-ports", 
> "/var/folders/7k/lgn577bj3cz8km_whdtw77k0gn/T/vagrant-sudo-helper20161128-28661-gawo5k"
> ]
> DEBUG subprocess: Command not in installer, not touching env vars.
>  INFO subprocess: Command is setuid/setgid, clearing DYLD_LIBRARY_PATH
> DEBUG subprocess: Selecting on IO
> DEBUG subprocess: stderr: /Users/simon/.vagrant.d/gems/gems/vagrant-vmware
> -fusion-4.0.15/bin/vagrant_vmware_desktop_sudo_helper:16:in `': 
> uninitialized constant Vagrant (NameError)
>  from 
> /Users/simon/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.15/bin/vagrant_vmware_desktop_sudo_helper:44:in
>  
> `RGLoader_load'
>  from 
> /Users/simon/.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.15/bin/vagrant_vmware_desktop_sudo_helper:44:in
>  
> `'
>
>

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/32a0feaf-23ca-4f75-a67b-4a6acaaa47fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Vagrant 1.9.0

2016-11-29 Thread croberts 
Hi everyone,

I'm pleased to announce the release of Vagrant 1.9.0. This release includes 
many improvements within Vagrant's internal plugin system. These 
improvements include: new commands for repairing or removing existing 
plugins, better isolation for Ruby version compatibility, and the removal 
of Bundler integration within Vagrant core. Please note that any installed 
plugins will have to be re-installed after this upgrade has been applied.

The full list of updates can be found in the CHANGELOG:

  
https://github.com/mitchellh/vagrant/blob/master/CHANGELOG.md#190-november-28-2016

Cheers!
- Chris Roberts

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/77ef87d4-dd5e-4862-8518-69b86ccf5f14%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vagrant-up] Vagrant 1.8.6

2016-09-30 Thread croberts 
Hi everyone,

I'm pleased to announce the release of Vagrant 1.8.6. This release includes 
a number of bug fixes and improvements. You can read the full CHANGELOG on 
GitHub.

  
https://github.com/mitchellh/vagrant/blob/master/CHANGELOG.md#186-september-27-2016

Cheers!
- Chris Roberts

-- 
This mailing list is governed under the HashiCorp Community Guidelines - 
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
--- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/49f48b11-4d6c-49b5-9e9c-ef594c16652c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.