Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#55163 - [vagrant] Using Vagrant with vmware workstation throws some odd file-existence errors from ruby
Attached to Project:
Community Packages
Opened by Ebrahim Azarisooreh (eazar001) - Wednesday, 16 August 2017, 03:46 GMT
Last edited by Jonathan Steel (jsteel) - Tuesday, 29 August 2017, 20:26 GMT
Opened by Ebrahim Azarisooreh (eazar001) - Wednesday, 16 August 2017, 03:46 GMT
Last edited by Jonathan Steel (jsteel) - Tuesday, 29 August 2017, 20:26 GMT
|
DetailsDescription:
After running `vagrant up` I get these lovely errors: [ebrahim@warmachine-alpha kyndi]$ vagrant up Bringing machine 'default' up with 'vmware_workstation' provider... ==> default: VMware requires root privileges to make many of the changes ==> default: necessary for Vagrant to control it. In a moment, Vagrant will ask for ==> default: your administrator password in order to install a helper that will have ==> default: permissions to make these changes. Note that Vagrant itself continues ==> default: to run without administrative privileges. [sudo] password for ebrahim: ==> default: Checking if box 'k-centos' is up to date... /home/ebrahim/.vagrant.d/gems/2.3.4/gems/vagrant-vmware-workstation-4.0.24/bin/vagrant_vmware_desktop_sudo_helper:20:in `stat': No such file or directory @ rb_file_s_stat - /opt/vagrant/embedded/lib/ruby/site_ruby/2.3.0 (Errno::ENOENT) from /home/ebrahim/.vagrant.d/gems/2.3.4/gems/vagrant-vmware-workstation-4.0.24/bin/vagrant_vmware_desktop_sudo_helper:20:in `block in <encoded>' from /home/ebrahim/.vagrant.d/gems/2.3.4/gems/vagrant-vmware-workstation-4.0.24/bin/vagrant_vmware_desktop_sudo_helper:19:in `delete_if' from /home/ebrahim/.vagrant.d/gems/2.3.4/gems/vagrant-vmware-workstation-4.0.24/bin/vagrant_vmware_desktop_sudo_helper:19:in `<encoded>' from /home/ebrahim/.vagrant.d/gems/2.3.4/gems/vagrant-vmware-workstation-4.0.24/bin/vagrant_vmware_desktop_sudo_helper:44:in `RGLoader_load' from /home/ebrahim/.vagrant.d/gems/2.3.4/gems/vagrant-vmware-workstation-4.0.24/bin/vagrant_vmware_desktop_sudo_helper:44:in `<main>' Additional info: * Vagrant 1.9.7 * I'm running a validated Vagrantfile for a centOS machine Steps to reproduce: 1) vagrant plugin install vagrant-vmware-workstation 2) vagrant up --provider=vmware_workstation 3) Get the error provided in my description above |
This task depends upon
Comment by Jonathan Steel (jsteel) -
Thursday, 24 August 2017, 18:05 GMT
You are better off reporting this issue upstream as I don't think this is a packaging issue. I'd start by reporting the issue against the vagrant-vmware-workstation plugin upstream.
Comment by Ebrahim Azarisooreh (eazar001) -
Friday, 25 August 2017, 05:29 GMT
OK, sure. I'll take this upstream.