-
-
Notifications
You must be signed in to change notification settings - Fork 642
Installing with php7.2 fails at composer install, referencing 7.3 extensions #1903
Comments
Strange, the default is currently PHP 7.2 and it seems to work okay... do you have any differences in your |
Overriding, no, not that I would know. |
I'm seeing a similar issue with the PHP versions. I've updated to the latest version of Drupal VM (1.2.5) on Mac and when I re-provisioned I can see that ansible was checking for the 7.2 versions of everything:
(This was the second run through so I would expect to see skipped here) But when I SSH in and run When I run
Cheers Tom |
I'm having the same issue as @tommym9. This occurs when running vagrant up to create a new box (I had just ran vagrant destroy on a box) I have "7.2" set in my config.yml file. Once vagrant up is completed and I ssh in, and run php -v, I see: Running composer global require drush/drush:7.* gave me an issue of curl extension not being installed and gave me a list of php 7.3 extensions like @tommym9. Thankfully, when I run vagrant provision and ssh back into the box, it's back to |
I'm having a very similar issue to @cloud-hybridforge and @tommym9; however, I'm not getting any failures on vagrant up, and re-provisioning does not seem to help get php to recognize the proper version, even after numerous tries. I'm not installing any extra packages, aside from uncommenting xdebug. Very odd indeed... |
I had the same issue on macOS with the old vagrant box After updating to 2.0.0 with |
I'm seeing a similar issue, using DrupalVM 4.9.2, wanting php 7.1, after "vagrant up", where the apache php version is correct (7.1), but the CLI version is php 7.3. After a subsequent "vagrant provision", the php CLI version seems to switch to the correct PHP 7.1 I'm still working on finding the "smoking gun" for why this happens. config.yml attached. |
My coworker and I are seeing the same issue as you, sphela02. I'm not sure if it's related to the original subject of this issue 🤔. |
i am seeing the same issue. Is there any update on this issue? |
I believe the above commit fixes this issue. Please try the latest master release and see if it's still an issue (I will be tagging a new release soon, as well). |
Excellent! I'll try it next week after the hurricane passes :) |
@sphela02 stay safe! Hopefully the whole storm diverts north... |
…eerlingguy#1964: Purge php-common package when installing different PHP version.
Issue Type
Your Environment
Your OS
Full console output
Summary
A fresh vargant up, with
php_version: "7.2"
in config fails to get past the composer install. When I runphp -v
, I getPHP 7.3.2-3+ubuntu16.04.1+deb.sury.org+1 (cli) (built: Feb 8 2019 15:43:26) ( NTS )
Obviously, this one misses packages (at least thephp-dom
).But running
does not resolve the issue, error remains, addressing /etc/php/7.3 modules.
Running
gets the composer install running. But this was not supposed to happen at all and I am unsure how to proceed - if the state is clean.
Afterwards,
vagrant provision
runs all the way through.php -v
resolves to an expectedPHP 7.2.15-1+ubuntu16.04.1+deb.sury.org+1 (cli) (built: Feb 8 2019 15:37:29) ( NTS )
.The text was updated successfully, but these errors were encountered: