The Vagrant base image is currently Stretch (Debian 9), which is EOL in 2020-07-06 (although the Debian LTS project supports it until 2022 summer). Wikimedia production and CI (which Vagrant is meant to be compatible with) are moving to Buster (Debian 10; T247045: Migrate all of production metal and VMs to Buster or later, T252432: Drop MediaWiki testing in stretch and instead test only in buster), MediaWiki-Vagrant should too.
See also:
- T245757: Upgrade MediaWiki clusters to Debian Buster (debian 10)
- T264991: Upgrade the MediaWiki servers to ICU 63
- T247045: Migrate all of production metal and VMs to Buster or later
- T252432: Drop MediaWiki testing in stretch and instead test only in buster
It's preferable to just recreate your Vagrant boxes from scratch (cattle not pets) but if you really need to upgrade an existing Stretch-based box, here are the steps:
- dump DB with mysqldump --add-drop-database --databases `mysql -rNe 'show databases' | ack -v '^(mysql|information_schema|performance_schema)$'` > /vagrant/dump.sql
- update Vagrant repo
- run vagrant destroy -f; vagrant up
- restore dump with mysql < /vagrant/dump.sql
- clear caches, e-g- by running vagrant reload
- regenerate all data wasn't stored in the DB:
- if the cirrussearch role is enabled, run mwscript /vagrant/mediawiki/extensions/CirrusSearch/maintenance/ForceSearchIndex.php
Previous: T181353: [EPIC] Migrate MediaWiki-Vagrant base image to Debian Stretch
Next: T319167: [EPIC] Upgrade MediaWiki-Vagrant to Debian Bullseye