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#54433 - Vagrant creates symlink with wrong path to binary
Attached to Project:
Community Packages
Opened by David Parrish (dmp1ce) - Tuesday, 13 June 2017, 11:08 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 13 June 2017, 13:48 GMT
Opened by David Parrish (dmp1ce) - Tuesday, 13 June 2017, 11:08 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 13 June 2017, 13:48 GMT
|
DetailsDescription:
After install vagrant running vagrant in bash shell doesn't work. The symlink path in /usr/bin appears to be wrong. Steps to reproduce: $ pacman -S vagrant $ vagrant bash: vagrant: command not found $ ls -alh /usr/bin/ | grep vagrant lrwxrwxrwx 1 root root 24 May 16 09:05 vagrant -> /opt/vagrant/bin/vagrant $ ls /opt/vagrant/bin ls: cannot access '/opt/vagrant/bin': No such file or directory |
This task depends upon
Closed by Doug Newgard (Scimmia)
Tuesday, 13 June 2017, 13:48 GMT
Reason for closing: Not a bug
Additional comments about closing: User requested: Part of vagrant-substrate was deleted on my machine. pacman -S vagrant-substrate fixed my issue.
Tuesday, 13 June 2017, 13:48 GMT
Reason for closing: Not a bug
Additional comments about closing: User requested: Part of vagrant-substrate was deleted on my machine. pacman -S vagrant-substrate fixed my issue.