search

geerlingguy / drupal-vm

A VM for Drupal development
https://www.drupalvm.com/
MIT License
1.37k stars 647 forks source link

'No package matching 'php7.3' is available' using box geerlingguy/ubuntu1604 #2179

Closed ameriel closed 2 years ago

ameriel commented 3 years ago

Issue Type

Your Environment

Vagrant 2.2.18
VirtualBox 6.1.26
ansible [core 2.11.3] 
  config file = None
  configured module search path = ['/Users/X/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/Cellar/ansible/4.4.0/libexec/lib/python3.9/site-packages/ansible
  ansible collection location = /Users/X/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/local/bin/ansible
  python version = 3.9.6 (default, Jun 29 2021, 05:25:02) [Clang 12.0.5 (clang-1205.0.22.9)]
  jinja version = 3.0.1
  libyaml = True

Your OS

Summary

Running 'vagrant up' would fail during the 'Ensure PHP packages are installed' task with an error saying 'No package matching 'php7.3' is available' (apologies - I didn't save the full output). However, when I switched the 'vagrant_box' value in config.yml from 'geerlingguy/ubuntu1604' to 'geerlingguy/ubuntu1804' it was able to finish without errors. (The reason we had it set to 1604 was because that is the value in BLT's config.yml apparently to match Acquia cloud environments.)

I decided to try that because of a thread I found after attempting to troubleshoot for quite a while: https://stackoverflow.com/questions/67891137/couldnt-upgrade-php-to-7-3-because-of-no-matching-package-is-available which says "...all the packages for the Ubuntu 16.04 LTS (Xenial) have been removed from the repositories."

I don't really know how any of this works - this may be more of an FYI for people who might also have this issue more than an actual bug report. This is all well outside of my skill set so please pardon my ignorance if I'm missing something obvious. :)

stale[bot] commented 2 years ago

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

stale[bot] commented 2 years ago

This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.