Updating PHP 5.1.6 to 17 on CentOS 5 via the Virtualmin bleed repository

Virtualmin
1

When I try to update PHP 5.1.6 to 17 via the Virtualmin bleed repository with “yum update php*” I get:

–> 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

I wonder - do I need to uninstall PHP first?

With rpm -qa | grep php I get:

php-pear-1.4.9-6.el5

php-pdo-5.1.6-27.el5_5.3

php-odbc-5.1.6-27.el5_5.3

php-xmlrpc-5.1.6-27.el5_5.3

php-mcrypt-5.1.6-15.el5.centos.1

wbm-php-pear-1.5-1

php-cli-5.1.6-27.el5_5.3

php-mysql-5.1.6-27.el5_5.3

php-imap-5.1.6-27.el5_5.3

php-mbstring-5.1.6-27.el5_5.3

php-gd-5.1.6-27.el5_5.3

php-devel-5.1.6-27.el5_5.3

php-common-5.1.6-27.el5_5.3

php-5.1.6-27.el5_5.3

php-pgsql-5.1.6-27.el5_5.3

php-snmp-5.1.6-27.el5_5.3

2

Oh I see, I didn’t catch this in your other post, but that particular yum update line would cause the trouble you’re seeing.

With “yum update php*”, that * would cause it to also try to upgrade the php53 packages, which you don’t want.

So, you could do “yum update php-*” if you want, including the “-” in there… or, you could just run “yum update” without any parameters, and it should pull down all the correct packages (if you setup the “includepkgs” line to only pull down PHP packages in your virtualmin.repo file).

-Eric

3

Ha!

“yum update” did the trick.

And now Wordpress upgrade to 3.2.1 is happy.

Many thanks Eric!

4

Great, I’m glad that worked!

-Eric