templates/locales/en.yml in vagrant-unbundled-1.9.5.1 vs templates/locales/en.yml in vagrant-unbundled-1.9.7.1

- old
+ new

@@ -20,10 +20,13 @@ Adding box '%{name}' (v%{version}) for provider: %{providers} box_added: |- Successfully added box '%{name}' (v%{version}) for '%{provider}'! box_adding_direct: |- Box file was not detected as metadata. Adding it directly... + box_add_url_warn: |- + It looks like you attempted to add a box with a URL for the name... + Instead, use box_url instead of box for box URLs. box_downloading: |- Downloading: %{url} box_download_error: |- Error downloading: %{message} box_unpacking: |- @@ -160,10 +163,14 @@ list_commands: |- Below is a listing of all available Vagrant commands and a brief description of what they do. %{list} + moved_cwd: |- + This machine used to live in %{old_wd} but it's now at %{current_wd}. + Depending on your current provider you may need to change the name of + the machine to run it as a different machine. guest_deb_installing_smb: |- Installing SMB "mount.cifs"... global_status_footer: |- The above shows information about all known Vagrant environments on this machine. This data is cached and may not be completely @@ -209,10 +216,12 @@ There are no paths to watch! This is either because you have no synced folders using rsync, or any rsync synced folders you have have specified `rsync_auto` to be false. rsync_auto_path: |- Watching: %{path} + rsync_auto_remove_folder: |- + Not syncing %{folder} as it is not part of the current working directory. rsync_auto_rsync_error: |- 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: @@ -378,11 +387,11 @@ The box you're attempting to add doesn't support the provider you requested. Please find an alternate box or use an alternate provider. Double-check your requested provider to verify you didn't simply misspell it. - If you're adding a box from HashiCorp's Atlas, make sure the box is + If you're adding a box from HashiCorp's Vagrant Cloud, make sure the box is released. Name: %{name} Address: %{url} Requested provider: %{requested} @@ -397,11 +406,11 @@ Constraints: %{constraints} Available versions: %{versions} box_add_short_not_found: |- The box '%{name}' could not be found or could not be accessed in the remote catalog. If this is a private - box on HashiCorp's Atlas, please verify you're logged in via + box on HashiCorp's Vagrant Cloud, please verify you're logged in via `vagrant login`. Also, please double-check the name. The expanded URL and error message are shown below: URL: %{url} Error: %{error} @@ -562,16 +571,16 @@ not installed. Please double-check and try again. The available versions for this box are: %{versions} box_server_not_set: |- - A URL to an Atlas server is not set, so boxes cannot be added with a + A URL to a Vagrant Cloud server is not set, so boxes cannot be added with a shorthand ("mitchellh/precise64") format. You may also be seeing this error if you meant to type in a path to a box file which doesn't exist locally on your system. - To set a URL to an Atlas server, set the `VAGRANT_SERVER_URL` + To set a URL to a Vagrant Cloud server, set the `VAGRANT_SERVER_URL` environmental variable. Or, if you meant to use a file path, make sure the path to the file is valid. box_update_multi_provider: |- You requested to update the box '%{name}'. This box has multiple providers. You must explicitly select a single @@ -1154,10 +1163,21 @@ shell_expand_failed: |- Vagrant failed to determine the shell expansion of a guest path (probably for one of your shared folders). This is an extremely rare error case and most likely indicates an unusual configuration of the guest system. Please report a bug with your Vagrantfile and debug log. + snapshot_force: |- + You must include the `--force` option to replace an existing snapshot. + snapshot_not_supported: |- + This provider doesn't support snapshots. + + This may be intentional or this may be a bug. If this provider + should support snapshots, then please report this as a bug to the + maintainer of the provider. + snapshot_not_found: |- + The snapshot name `%{snapshot_name}` was not found for the + virtual machine `%{machine}`. ssh_authentication_failed: |- SSH authentication failed! This is typically caused by the public/private keypair for the SSH user not being properly set on the guest VM. Please verify that the guest VM is setup with the proper public key, and that the private key path for Vagrant is setup properly as well. @@ -1535,19 +1555,19 @@ instructed. Due to the inability to enforce expected Linux file ownership and permissions on the Windows system, Vagrant will not make modifications to prevent unexpected errors. To learn more about this, and the options that are available, please refer to the Vagrant documentation: - https://www.vagrantup.com/docs/other/wsl + https://www.vagrantup.com/docs/other/wsl.html wsl_virtualbox_windows_access: |- Vagrant is unable to use the VirtualBox provider from the Windows Subsystem for Linux without access to the Windows environment. Enabling this access must be 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 + https://www.vagrantup.com/docs/other/wsl.html #------------------------------------------------------------------------------- # Translations for config validation errors #------------------------------------------------------------------------------- config: common: @@ -2341,9 +2361,12 @@ windows_not_supported_for_control_machine: |- Windows is not officially supported for the Ansible Control Machine. Please check https://docs.ansible.com/intro_installation.html#control-machine-requirements docker: + wrong_provisioner: |- + The Docker post-install provisioner cannot also take a Docker post-install + provisioner not_running: "Docker is not running on the guest VM." install_failed: "Docker installation failed." salt: minion_config_nonexist: |-