On 30 April 2011 07:35, Eero Volotinen eero.volotinen@iki.fi wrote:

2011/4/30 Dave Cross davorg@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...

On Sun, May 01, 2011 at 08:19:49AM +0100, Lucian wrote:

It's not really that risky, just rpm -e --nodeps and then yum install php53 packages.

Do not follow this advice at all; it will most likely wreck your server.

Contact Plesk support or your hosting provider's support department and ask them about upgrading php. Plesk, like most control panels, integrates quite tightly into your system; replacing the system default php-5.1.6 with the php53 optional package may not be supported for your environment.

John

On Sun, May 01, 2011 at 09:40:13AM +0100, Dave Cross wrote:

This is exactly what worried me. Thanks for confirming my fears.

Something else I should have pointed out earlier is that the php53 package from TUV does _not_ have a Provide: php in effect; meaning that this is not a fully drop-in replacement for the default version and will cause issues if you try to use it with packages that require "php" to be provided for - squirrelmail is one such example of a package that CentOS provides that will not work with php53 but there are many others.

There are some other issues present with php53 as well. People needing php53 support may very well be happier with the package as provided by the IUS repository; it's more complete and more compatible than the one that TUV is supplying. More information on IUS is available at:

http://wiki.centos.org/AdditionalResources/Repositories

Please take a few moments and read the IUS web page that's linked off the CentOS wiki article in its entirety to understand how IUS works.

John

On Sun, May 1, 2011 at 8:50 AM, John R. Dennison jrd@gerdesas.com wrote:

On Sun, May 01, 2011 at 08:19:49AM +0100, Lucian wrote:

...

It's not really that risky, just rpm -e --nodeps and then yum install php53 packages.

Do not follow this advice at all; it will most likely wreck your server.

Contact Plesk support or your hosting provider's support department and ask them about upgrading php.  Plesk, like most control panels, integrates quite tightly into your system; replacing the system default php-5.1.6 with the php53 optional package may not be supported for your environment.

Plesk uses stock PHP (one of the smarter things about Plesk) so you can pretty much play around with it. The problem here is indeed the fact that php53 from RH doesn't "Provide" "php" (other repos have this fixed, ius etc). What I advised wouldn't have "horribly" broken his setup; fixing it would've been as simple and fast as uninstalling php53 and reinstalling old php 5.1, 1 minute job.