It looks to me like the wiki page for smeserver-scl-php now assumes that the remi-safe repository is "enabled" instead of "disabled".
You have two choices:
* Permanently "enable" the remi-safe repository
* Temporarily enable remi-safe when updating smecontribs-scl-php
I do not believe in permanently enabling non-standard repositories, but if you want to do that you would use:
db yum_repositories setprop remi-safe status enabled
expand-template /etc/yum.smerepos.d/sme-base.repo
Confirm success by executing "yum repolist":
# yum repolist
Loaded plugins: fastestmirror, post-transaction-actions, smeserver
Loading mirror speeds from cached hostfile
* base: centos2.zswap.net
* smeaddons: mirror.canada.pialasse.com
* smeextras: mirror.canada.pialasse.com
* smeos: mirror.canada.pialasse.com
* smeupdates: mirror.canada.pialasse.com
* updates: centos2.zswap.net
base | 3.7 kB 00:00
remi-safe | 3.0 kB 00:00
remi-safe/primary_db | 1.1 MB 00:00
smeaddons | 2.9 kB 00:00
smeextras | 2.9 kB 00:00
smeos | 3.1 kB 00:00
smeupdates | 2.9 kB 00:00
updates | 3.4 kB 00:00
repo id repo name status
base CentOS - os 6,710+3
remi-safe Remi - safe 2,730
smeaddons SME Server - addons 28
smeextras SME Server - extras 165
smeos SME Server - os 1,810
smeupdates SME Server - updates 138
updates CentOS - updates 250+1
repolist: 11,831
If like me you prefer to leave all non-standard repositories disabled, you can enable the repo while you update smecontribs-php-scl:
yum --enablerepo=smecontribs --enablerepo=remi-safe update smecontribs-php-scl
Once "smecontribs-php-scl" has been updated from smecontribs, and all of the dependent php7x- and php5x- packages have been updated from remi-safe, run a second update to update smeserver-letsencrypt:
yum --enablerepo=smecontribs update