Running transaction check
--> Processing Dependency: php = 4.3.11-2.8 for package: php-domxml
--> Finished Dependency Resolution
Error: Missing Dependency: php = 4.3.11-2.8 is needed by package php-domxml
Any suggestions? It seems php-domxml is required by the psa-horde package which I don't want to break by removing the RPM.
I found another thread where the same error occurred and it was suggested to run "yum update" without specifying the MySQL package specifically, but I don't want to update PHP and all the other packages.
[root@server ~]# yum upgrade mysql
Repository updates-released already added, not adding again
Repository base already added, not adding again
Setting up Upgrade Process
Setting up Repos
base 100% |=========================| 1.1 kB 00:00
atomic 100% |=========================| 951 B 00:00
updates-released 100% |=========================| 951 B 00:00
Reading repository metadata in from local files
base : ################################################## 2622/2622
atomic : ################################################## 254/254
updates-re: ################################################## 910/910
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package mysql.i386 0:4.1.21-2.rhfc3.art set to be updated
--> Running transaction check
--> Processing Dependency: libmysqlclient.so.10 for package: php-mysql
--> Processing Dependency: libmysqlclient.so.10 for package: perl-DBD-MySQL
--> Processing Dependency: libmysqlclient.so.10 for package: mysql-server
--> Processing Dependency: libmysqlclient.so.10 for package: sitebuilder-core
--> Processing Dependency: mysql = 3.23.58 for package: mysql-server
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Package mysql-compat.i386 0:4.1.21-2.rhfc3.art set to be updated
---> Package mysql-server.i386 0:4.1.21-2.rhfc3.art set to be updated
---> Package php-mysql.i386 0:5.0.4-13.rhfc3.art set to be updated
--> Running transaction check
--> Processing Dependency: php = 5.0.4-13.rhfc3.art for package: php-mysql
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Package php.i386 0:5.0.4-13.rhfc3.art set to be updated
--> Running transaction check
--> Processing Dependency: php = 4.3.11-2.8 for package: php-imap
--> Processing Dependency: php = 4.3.11-2.8 for package: php-pgsql
--> Processing Dependency: php = 4.3.11-2.8 for package: php-pear
--> Processing Dependency: php = 4.3.11-2.8 for package: php-domxml
--> Processing Dependency: php = 4.3.11-2.8 for package: php-gd
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Package php-pear.i386 0:5.0.4-13.rhfc3.art set to be updated
---> Package php-imap.i386 0:5.0.4-13.rhfc3.art set to be updated
---> Package php-pgsql.i386 0:5.0.4-13.rhfc3.art set to be updated
---> Package php-gd.i386 0:5.0.4-13.rhfc3.art set to be updated
--> Running transaction check
--> Processing Dependency: php = 4.3.11-2.8 for package: php-domxml
--> Finished Dependency Resolution
Error: Missing Dependency: php = 4.3.11-2.8 is needed by package php-domxml
[root@server ~]#
Thanks for your help. Do you know if it will be safe to upgrade MySQL without upgrading the PHP packages? Since it's on a working system I don't want to break anything... thanks.
Its completely safe to just upgrade mysql, the only package that depends on it is php 5.0/5.1 which are linked against mysql 4.1 and above. Just bumping up mysql alone shouldnt cause any problems.
[root@server ~]# yum upgrade mysql
Repository updates-released already added, not adding again
Repository base already added, not adding again
Setting up Upgrade Process
Setting up Repos
base 100% |=========================| 1.1 kB 00:00
atomic 100% |=========================| 951 B 00:00
updates-released 100% |=========================| 951 B 00:00
Reading repository metadata in from local files
base : ################################################## 2622/2622
atomic : ################################################## 254/254
updates-re: ################################################## 910/910
Excluding Packages from Atomic Rocket Turtle - 3 - Atomic PSA-Compatible RPMS
Finished
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package mysql.i386 0:4.1.21-2.rhfc3.art set to be updated
--> Running transaction check
--> Processing Dependency: libmysqlclient.so.10 for package: php-mysql
--> Processing Dependency: libmysqlclient.so.10 for package: perl-DBD-MySQL
--> Processing Dependency: libmysqlclient.so.10 for package: mysql-server
--> Processing Dependency: libmysqlclient.so.10 for package: sitebuilder-core
--> Processing Dependency: mysql = 3.23.58 for package: mysql-server
--> Restarting Dependency Resolution with new changes.
--> Populating transaction set with selected packages. Please wait.
---> Package mysql-compat.i386 0:4.1.21-2.rhfc3.art set to be updated
---> Package mysql-server.i386 0:4.1.21-2.rhfc3.art set to be updated
--> Running transaction check
Dependencies Resolved
Transaction Listing:
Update: mysql.i386 0:4.1.21-2.rhfc3.art - atomic
Performing the following to resolve dependencies:
Install: mysql-compat.i386 0:4.1.21-2.rhfc3.art - atomic
Update: mysql-server.i386 0:4.1.21-2.rhfc3.art - atomic
Total download size: 14 M
Is this ok [y/N]: y
Downloading Packages:
(1/3): mysql-compat-4.1.2 100% |=========================| 249 kB 00:00
(2/3): mysql-server-4.1.2 100% |=========================| 10 MB 00:17
(3/3): mysql-4.1.21-2.rhf 100% |=========================| 3.6 MB 00:09
warning: rpmts_HdrFromFdno: V3 DSA signature: NOKEY, key ID 5ebd2744
public key not available for mysql-compat-4.1.21-2.rhfc3.art.i386.rpm
[root@server~]#
Well, it says you don't have the public key. Every page on 3es.atomicrocketturtle.com has the instructions for installing ART's GPG key:
GPG Key
ART packages are signed with GPG. This is to ensure that the packages have not been tampered with. ART packages that fail the gpg check should be reported immediatly.