Topic: Problem upgrading from stock CentOS-7 php to Remi php >= 7.0
Hi,
I'm trying to package a recent version of nextcloud for CentOS-7.
I started from nextcloud-10.0.4 present in EPEL and was able to upgrade it to 10.0.6. Unfortunately this version is now obsolete and the desktop client is unable to connect to it.
As the EPEL ticket about newer versions is stalled I decided to give a try to create package from 11.0 to latest one so one can upgrade from 10 to 17 with all the migrations in between.
I have a package that builds for V11, but it requires a php version higher than stock CentOS-7. Hence my prence here.
My problem is that installing Remi's package won't upgrade all php packages (only core OS package; not EPEL ones) resulting with a system with updated php engine and left with old stuffs that are not in Remis's repo.
If I remove all old php package and nextcloud keeping all Remi's php packages and if I try to install my non working nextcloud package, it tries to install many EPEL-php packages that are linked with old stock centos-7 php libs:
Of cours if I do that, I get plenty of modules loading errors, lib mismatches , etc...
I'm far from being expert in php, and I was really happy to find Remi's repos that do system replacement instead of parallel install that often require specific adjustments in config and paths.
Though, I'm stuck as I don't know how to handle the lack of packages like php-symfony-* and many others.
Did I forgot to enable a Remi-epel repo for all EPEL php modules?
If not how can I handle the miss of all those packages?
Many thanks for any tips. (If I succeed to build and upgrade nextcloud, of course I'll share my packages and src.rpm)
Cheers,
Olivier.