templates/locales/en.yml in vagrant-unbundled-2.2.19.0 vs templates/locales/en.yml in vagrant-unbundled-2.3.2.0

- old
+ new

@@ -613,10 +613,16 @@ File: %{file} box_metadata_corrupted: |- The metadata associated with the box '%{name}' appears corrupted. This is most often caused by a disk issue or system crash. Please remove the box, re-add it, and try again. + box_metadata_missing_required_fields: |- + The metadata associated with the box '%{name}' appears to be missing + the required field '%{required_field}'. Please ensure `metadata.json` + has all required fields. + + Required fields: %{all_fields} box_metadata_download_error: |- There was an error while downloading the metadata for this box. The error message is shown below: %{message} @@ -711,10 +717,19 @@ directly instead of from a box catalog. Vagrant can only check the versions of boxes that were added from a catalog such as from the public Vagrant Server. box_update_no_name: |- This machine doesn't have a box. Won't update anything. + box_version_invalid: |- + The format of box version provided (%{version}) is incorrect. The + version must follow the semantic versioning format or semantic + versioning compatible constraint format. Examples of valid values: + + 2.0 + 2.1.4 + >= 2 + < 3.0.0 bundler_disabled: |- Vagrant's built-in bundler management mechanism is disabled because Vagrant is running in an external bundler environment. In these cases, plugin management does not work with Vagrant. To install plugins, use your own Gemfile. To load plugins, either put the @@ -1670,10 +1685,12 @@ an invalid or undefined variable. Path: %{path} Line number: %{line} Message: %{message} + vagrant_remote_error: |- + %{msg} vagrantfile_syntax_error: |- There is a syntax error in the following Vagrantfile. The syntax error message is reproduced below for convenience: %{file} @@ -1724,9 +1741,14 @@ virtualbox_broken_version_040214: |- Vagrant detected you have VirtualBox 4.2.14 installed. VirtualBox 4.2.14 contains a critical bug which prevents it from working with Vagrant. VirtualBox 4.2.16+ fixes this problem. Please upgrade VirtualBox. + virtualbox_config_not_found: |- + Vagrant was unable to locate the configuration file for the requested + VirtualBox VM. Verify the requested VM exists and try again. + + UUID provided: %{uuid} virtualbox_disks_controller_not_found: |- Vagrant expected to find a storage controller called '%{name}', but there is no controller with this name attached to the current VM. If you have changed or removed any storage controllers, please restore them to their previous configuration.