en.yml in vagrant-unbundled-2.2.3.0

- old
+ new

@@ -44,11 +44,11 @@
       Could not determine box updates because box metadata was malformed.
       Vagrant will continue on...
     box_outdated: |-
       * '%{name}' for '%{provider}' is outdated! Current: %{current}. Latest: %{latest}
     box_outdated_checking_with_refresh: |-
-      Checking if box '%{name}' is up to date...
+      Checking if box '%{name}' version '%{version}' is up to date...
     box_outdated_local: |-
       A newer version of the box '%{name}' is available and already
       installed, but your Vagrant machine is running against
       version '%{old}'. To update to version '%{new}',
       destroy and recreate your machine.
@@ -233,10 +233,16 @@
       There was an error while executing rsync. The error is shown below.
       This may not be critical since rsync sometimes fails, but if this message
       repeats, then please fix the issue:
 
       %{message}
+    rsync_auto_post_command_error: |-
+      There was an error while executing the rsync post command. This error is
+      shown below. This may not be critical but if this message repeats please
+      fix the issue:
+
+      %{message}
     rsync_communicator_not_ready: |-
       The machine is reporting that it is not ready for rsync to
       communicate with it. Verify that this machine is properly running.
     rsync_communicator_not_ready_callback: |-
       Failed to connect to remote machine. This is usually caused by the
@@ -391,10 +397,22 @@
         compatible, there are some cases where things have changed
         significantly enough to warrant a message. These messages are
         shown below.
 
         %{output}
+      experimental:
+        all: |-
+          You have enabled the experimental flag with all features enabled.
+          Please use with caution, as some of the features may not be fully
+          functional yet.
+        features: |-
+          You have requested to enabled the experimental flag with the following features:
+
+          Features:  %{features}
+
+          Please use with caution, as some of the features may not be fully
+          functional yet.
       not_in_installer: |-
         You appear to be running Vagrant outside of the official installers.
         Note that the installers are what ensure that Vagrant has all required
         dependencies, and Vagrant assumes that these dependencies exist. By
         running outside of the installer environment, Vagrant may not function
@@ -566,10 +584,15 @@
       box_config_changing_box: |-
         While loading the Vagrantfile, the provider override specified
         a new box. This box, in turn, specified a different box. This isn't
         allowed, as it could lead to infinite recursion of Vagrant configuration
         loading. Please fix this.
+      box_file_not_exist: |-
+        The file you are attempting to upload does not exist. Please recheck
+        that the file exists and was passed in correctly.
+
+        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_download_error: |-
@@ -1252,10 +1275,18 @@
 
         Host path: %{hostpath}
         Guest path: %{guestpath}
         Command: %{command}
         Error: %{stderr}
+      rsync_post_command_error: |-
+        There was an error while attempting to run the post rsync
+        command for a synced folder. Please inspect the error message
+        below for more info.
+
+        Host path: %{hostpath}
+        Guest path: %{guestpath}
+        Error: %{message}
       rsync_guest_install_error: |-
         Installation of rsync into the guest has failed! The stdout
         and stderr are shown below. Please read the error output, resolve
         it and try again. If the problem persists, please install rsync
         manually within the guest.
@@ -1791,10 +1822,11 @@
       ssh:
         private_key_missing: "`private_key_path` file must exist: %{path}"
         paranoid_deprecated: |-
           The key `paranoid` is deprecated. Please use `verify_host_key`. Supported
           values are exactly the same, only the name of the option has changed.
+        ssh_config_missing: "`config` file must exist: %{path}"
       triggers:
         bad_command_warning: |-
           The command '%{cmd}' was not found for this trigger.
         name_bad_type: |-
           Invalid type set for `name` on trigger for command '%{cmd}'. `name` should be a String.
@@ -2289,10 +2321,12 @@
           disabled_by_config: |-
             Machine not provisioned because `--no-provision` is specified.
           disabled_by_sentinel: |-
             Machine already provisioned. Run `vagrant provision` or use the `--provision`
             flag to force provisioning. Provisioners marked to run always will still run.
+          file:
+            locations: "%{src} => %{dst}"
         resume:
           resuming: Resuming suspended VM...
           unpausing: |-
             Unpausing the VM...
         share_folders:
@@ -2699,12 +2733,14 @@
         missing_key: |-
           You must include both public and private keys.
         must_accept_keys: |-
           You must accept keys when running highstate with master!
         args_array: |-
-          You must set this value as an array.
+          You must set `args_array` value as an array.
         python_version: |-
-          You must set this as an integer or string that represents an integer.
+          You must set `python_version` as an integer or string that represents an integer.
+        version_type_missing: |-
+          You must set the option `install_type` when specifying a `version`.
 
     pushes:
       file:
         no_destination: "File destination must be specified."