-
Notifications
You must be signed in to change notification settings - Fork 397
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DrupalVM init fails due to missing package php-bz2 #521
Comments
@danepowell - see my note on #502: #502 (comment) |
To fix in the interim, make the following changes to your
|
(That should hopefully keep things working with PhantomJS, since the PECL install will get |
Thanks, we can work around it locally in the meantime but I do think it would be good to have it build cleanly before the next release, whichever route that implies. |
@danepowell Can you share your workaround? @geerlingguy's changes alone do not seem to be enough. |
I'm sorry to say that our "workaround" was just to remove the bz2 package from the configuration altogether, since we don't run Behat tests within the VM. I don't know of any workaround that would allow you to provision the VM and run PhantomJS in it, other than what @geerlingguy proposed. |
PhantomJS has been replaced with Selenium. I'm still working out Drupal VM integration issues. Will be in next released. |
FYI, Alex's Selenium role is almost to a point where it can get a new tagged release, and the new default will be Chrome instead of Firefox. I'll get Drupal VM updated ASAP after that. |
The php-bz2 package defined in config.yml doesn't exist for Ubuntu Trusty, causing Vagrant provisioning to fail.
This only became a problem yesterday when the DrupalVM box was downgraded from Xenial to Trusty. See #501 and #502.
The text was updated successfully, but these errors were encountered: