[CentOS] Switching to php53

[Dave Cross]

On 30 April 2011 07:35, Eero Volotinen <eero.volotinen at iki.fi> wrote:
> 2011/4/30 Dave Cross <davorg at gmail.com>:
>> I have a Centos 5.6 server which is using the default php packages.
>> These currently contain PHP 5.1.6.
>>
>> My main use of PHP on the server is to support an installation of
>> WordPress. I currently had WP 3.1.2 installed, but the WP developers
>> have announced that from WP 3.2 they will only support PHP 5. and
>> greater.
>>
>> So I investigated and found that the Centos repo contains a series of
>> php53 packages. I tried to install php53 using yum but got the
>> following error:
>>
>>  Resolving Dependencies
>>  --> Running transaction check
>>  ---> Package php53.x86_64 0:5.3.3-1.el5_6.1 set to be updated
>>  --> Processing Dependency: php53-cli = 5.3.3-1.el5_6.1 for package: php53
>>  --> Processing Dependency: php53-common = 5.3.3-1.el5_6.1 for package: php53
>>  --> Running transaction check
>>  ---> Package php53-cli.x86_64 0:5.3.3-1.el5_6.1 set to be updated
>>  ---> Package php53-common.x86_64 0:5.3.3-1.el5_6.1 set to be updated
>>  --> Processing Conflict: php53-common conflicts php-common
>>  --> Finished Dependency Resolution
>>  php53-common-5.3.3-1.el5_6.1.x86_64 from updates has depsolving problems
>>    --> php53-common conflicts with php-common
>>  Error: php53-common conflicts with php-common
>>   You could try using --skip-broken to work around the problem
>>   You could try running: package-cleanup --problems
>>                          package-cleanup --dupes
>>                          rpm -Va --nofiles --nodigest
>>
>> I would have thought that the new php53-common package would have
>> obsoleted php-common rather than conflicting with it.
>>
>> Is there a clean way to replace php with php53? Or should I just wait
>> and hope that Centos 6 is released before WP 3.2 :)
>
> just remove php and php-common
>
> yum remove php php-common

Er... that looks like it wants to take another 109 packages with it.
Most of which seem to be connected with Plesk. And that's pretty
fundamental to the working of this server.

So that all sounds like a rather risky strategy.

Cheers,

Dave...

-- 
Dave Cross :: dave at dave.org.uk
http://dave.org.uk/
@davorg