vagrant@vagrant:~$ apt policy php
php:
Installed: 2:7.2+69+0~20190215163918.14+stretch~1.gbpfa617b+wmf1
Candidate: 2:7.2+69+0~20190215163918.14+stretch~1.gbpfa617b+wmf1
Version table:
*** 2:7.2+69+0~20190215163918.14+stretch~1.gbpfa617b+wmf1 1001
1001 http://apt.wikimedia.org/wikimedia stretch-wikimedia/component/php72 amd64 Packages
100 /var/lib/dpkg/status
1:7.0+49 500
500 http://deb.debian.org/debian stretch/main amd64 Packages
vagrant@vagrant:~$ apt policy php7.2
php7.2:
Installed: 7.2.31-1+0~20200514.41+debian9~1.gbpe2a56b+wmf1
Candidate: 7.2.31-1+0~20200514.41+debian9~1.gbpe2a56b+wmf1
Version table:
*** 7.2.31-1+0~20200514.41+debian9~1.gbpe2a56b+wmf1 1001
1001 http://apt.wikimedia.org/wikimedia stretch-wikimedia/component/php72 amd64 Packages
100 /var/lib/dpkg/statusThe first of those is PHP 7.2.16 which doesn't even work with current versions of MediaWiki (which require 7.2.22+). Not sure if it's intentional, but it's pretty confusing.
Seen on vagrant, which pins apt.wikimedia.org:
/etc/apt/preferences.d/wikimedia.pref
Package: * Pin: release o=Wikimedia Pin-Priority: 1001
/etc/apt/sources.list.d/wikimedia-php.list
deb http://apt.wikimedia.org/wikimedia stretch-wikimedia component/php72 deb-src http://apt.wikimedia.org/wikimedia stretch-wikimedia component/php72
(Note that my understanding of APT is very superficial so I might have made some rookie mistake here like not disabling some cache. But the two apt policy commands give different results on the same vagrant box, right after an apt update, which AFAICS shouldn't happen.)