haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

More wording changes on version conflicts

This commit is contained in:
Mitchell Hashimoto 2014-03-09 22:47:56 -07:00
parent c391d2d46b
commit bc31abe125
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
bin/vagrant
View File

@ -61,9 +61,11 @@ begin
Bundler.setup(:default, :plugins) Bundler.setup(:default, :plugins)
rescue Bundler::VersionConflict => e rescue Bundler::VersionConflict => e
$stderr.puts "Vagrant experienced a version conflict with some installed plugins!" $stderr.puts "Vagrant experienced a version conflict with some installed plugins!"
$stderr.puts "If you recently upgraded Vagrant, the recommended way to fix this is" $stderr.puts "This usually happens if you recently upgraded Vagrant. As part of the"
$stderr.puts "to remove your existing plugins and reinstall them one-by-one. To" $stderr.puts "upgrade process, some existing plugins are no longer compatible with"
$stderr.puts "remove all plugins:" $stderr.puts "this version of Vagrant. The recommended way to fix this is to remove"
$stderr.puts "your existing plugins and reinstall them one-by-one. To remove all"
$stderr.puts "plugins:"
$stderr.puts "" $stderr.puts ""
$stderr.puts " rm -r ~/.vagrant.d/plugins.json ~/.vagrant.d/gems" $stderr.puts " rm -r ~/.vagrant.d/plugins.json ~/.vagrant.d/gems"
$stderr.puts "" $stderr.puts ""