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#53982 - [vagrant] Can't run homestead vm
Attached to Project:
Community Packages
Opened by anptr (anptr) - Tuesday, 09 May 2017, 08:57 GMT
Last edited by Jonathan Steel (jsteel) - Wednesday, 10 May 2017, 17:14 GMT
Opened by anptr (anptr) - Tuesday, 09 May 2017, 08:57 GMT
Last edited by Jonathan Steel (jsteel) - Wednesday, 10 May 2017, 17:14 GMT
|
DetailsDescription:
After latest update i can't run homestead vm. Additional info: * package version(s) * config and/or log files etc. Version 1.9.4-1 Steps to reproduce: After command "vagrant up" i get error for each configured site There are errors in the configuration of this machine. Please fix the following errors and try again: shell provisioner: * Shell provisioner `args` must be a string or array. |
This task depends upon
Comment by Jonathan Steel (jsteel) -
Wednesday, 10 May 2017, 16:12 GMT
Please share your Vagrantfile so I can try and replicate the issue you are seeing. I do suspect this issue should be one for upstream rather than an issue specifically with Arch's package.
Comment by anptr (anptr) -
Wednesday, 10 May 2017, 16:40 GMT
Yes, latest update from homested developers fixes error. It is not arch related.