templates/locales/en.yml in vagrant-unbundled-2.0.2.0 vs templates/locales/en.yml in vagrant-unbundled-2.0.3.0
- old
+ new
@@ -300,11 +300,11 @@
https://www.vagrantup.com/downloads.html
If you're curious what changed in the latest release, view the
CHANGELOG below:
- https://github.com/mitchellh/vagrant/blob/v%{version}/CHANGELOG.md
+ https://github.com/hashicorp/vagrant/blob/v%{version}/CHANGELOG.md
cfengine_config:
classes_array: |-
The 'classes' configuration must be an array.
files_path_not_directory: |-
@@ -844,10 +844,14 @@
host_explicit_not_detected: |-
The host implementation explicitly specified in your Vagrantfile
("%{value}") could not be found. Please verify that the plugin is
installed which implements this host and that the value you used
for `config.vagrant.host` is correct.
+ hyperv_virtualbox_error: |-
+ Hyper-V and VirtualBox cannot be used together and will result in a
+ system crash. Vagrant will now exit. Please disable Hyper-V if you wish
+ to use VirtualBox.
interrupted: |-
Vagrant exited after cleanup due to external interrupt.
local_data_dir_not_accessible: |-
The directory Vagrant will use to store local environment-specific
state is not accessible. The directory specified as the local data
@@ -1161,11 +1165,11 @@
If you'd like this provisioner to work over WinRM, please
take a look at the Vagrant source code linked below and try
to contribute back support. Thank you!
- https://github.com/mitchellh/vagrant
+ https://github.com/hashicorp/vagrant
rsync_error: |-
There was an error when attempting to rsync a synced folder.
Please inspect the error message below for more info.
Host path: %{hostpath}
@@ -1623,10 +1627,14 @@
done with caution and an understanding of the implications. For more information
on enabing Windows access and using VirtualBox from the Windows Subsystem for
Linux, please refer to the Vagrant documentation:
https://www.vagrantup.com/docs/other/wsl.html
+ wsl_rootfs_not_found_error: |-
+ Vagrant is unable to determine the location of this instance of the Windows
+ Subsystem for Linux. If this error persists it may be resolved by destroying
+ this subsystem and installing it again.
#-------------------------------------------------------------------------------
# Translations for config validation errors
#-------------------------------------------------------------------------------
config:
common:
@@ -2384,11 +2392,11 @@
If you'd like this provisioner to be improved, please
take a look at the Vagrant source code linked below and try
to contribute back support. Thank you!
- https://github.com/mitchellh/vagrant
+ https://github.com/hashicorp/vagrant
errors:
ansible_command_failed: |-
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.
ansible_compatibility_mode_conflict: |-
@@ -2421,20 +2429,20 @@
Internal Details:
%{details}
Sorry, but this Vagrant error should never occur.
- Please check https://github.com/mitchellh/vagrant/issues for any
+ Please check https://github.com/hashicorp/vagrant/issues for any
existing bug report. If needed, please create a new issue. Thank you!
cannot_support_pip_install: |-
Unfortunately Vagrant does not support yet installing Ansible
from pip for the guest OS running in the machine.
If you'd like this provisioner to be improved, please
take a look at the Vagrant source code linked below and try
to contribute back support. Thank you!
- https://github.com/mitchellh/vagrant
+ https://github.com/hashicorp/vagrant
ansible_version_mismatch: |-
The requested Ansible version (%{required_version}) was not found on the %{system}.
Please check the Ansible installation on your Vagrant %{system} system (currently: %{current_version}),
or adapt the provisioner `version` option in your Vagrantfile.
See https://docs.vagrantup.com/v2/provisioning/ansible_common.html#version