-
-
Save ocxo/ce376fb4ab3298392048 to your computer and use it in GitHub Desktop.
| # temporary hack to address bug with vagrant-vbguest installation | |
| # https://github.com/mitchellh/vagrant/issues/4962 | |
| if awk "BEGIN {exit `vagrant -v` == "1.7.1" ? 0 : 1 }" | |
| then | |
| sudo sed -i .original 's/\*\*opts/opts/g' /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/machine.rb | |
| fi |
Anybody help me with this fix, alas Im using Windows 7 x64. Thanks.
Cannot box anything.
Confirmed 1.7.2 does indeed fix this problem. Prior to upgrading to 1.7.2 myself, I was getting this:
~/VAGRANT/BRONZE ᐅ vagrant package --output silver.box
/opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/machine.rb:153:in action': wrong number of arguments (2 for 1) (ArgumentError) from /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/plugins/commands/package/command.rb:83:inpackage_vm'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/plugins/commands/package/command.rb:72:in block in package_target' from /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/plugin/v2/command.rb:226:inblock in with_target_vms'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/plugin/v2/command.rb:220:in each' from /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/plugin/v2/command.rb:220:inwith_target_vms'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/plugins/commands/package/command.rb:70:in package_target' from /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/plugins/commands/package/command.rb:44:inexecute'
from /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/cli.rb:42:in execute' from /opt/vagrant/embedded/gems/gems/vagrant-1.7.1/lib/vagrant/environment.rb:301:incli'
from /opt/vagrant/bin/../embedded/gems/gems/vagrant-1.7.1/bin/vagrant:174:in `
cool, this solved the packaging problem for me, btw, how do you find this bug?
find it using --debug message? but it seems the error message is not in the debug infomation, so how do you locate this bug?
Life saver! Thanks @fromonesrc