Re: mysql-libs dependancy not met in CentOS/RHEL 6
Where's the spec file? mysql52-ourdelta-centos.spec isn't even in the official ourdelta repo.

Re: mysql-libs dependancy not met in CentOS/RHEL 6
Hi Joe - note that the builds of MariaDB are now handled at Monty Program - it's based on the work we did at OurDelta, but has been extended and updated since. So that's why you didn't see anything for 5.2 in the trunk.
The current version that Monty Program uses is in a branch owned by knielsen.
I've added the Maria project to this bug report, so they can review as appropriate.

Launchpad bug id: 913489

This bug is still present in RHEL6 with MariaDB-server-galera 5.5.34 installed. It affects postfix as mentioned but also perl-DBD-MySQL so I can't install mytop because it depends on this package.

--> Finished Dependency Resolution
Error: Package: perl-DBD-MySQL-4.013-3.el6.x86_64 (rhel-6-server-rpms)
Requires: libmysqlclient.so.16()(64bit)
Available: mysql-libs-5.1.47-4.el6.x86_64 (rhel-6-server-rpms)
libmysqlclient.so.16()(64bit)
Available: mysql-libs-5.1.52-1.el6_0.1.x86_64 (rhel-6-server-rpms)
libmysqlclient.so.16()(64bit)
Available: mysql-libs-5.1.61-1.el6_2.1.x86_64 (rhel-6-server-rpms)
libmysqlclient.so.16()(64bit)
Available: mysql-libs-5.1.61-4.el6.x86_64 (rhel-6-server-rpms)
libmysqlclient.so.16()(64bit)
Available: mysql-libs-5.1.66-1.el6_3.x86_64 (rhel-6-server-rpms)
libmysqlclient.so.16()(64bit)
Available: mysql-libs-5.1.66-2.el6_3.x86_64 (rhel-6-server-rpms)
libmysqlclient.so.16()(64bit)
Available: mysql-libs-5.1.67-1.el6_3.x86_64 (rhel-6-server-rpms)
libmysqlclient.so.16()(64bit)
Available: mysql-libs-5.1.69-1.el6_4.x86_64 (rhel-6-server-rpms)
libmysqlclient.so.16()(64bit)
Available: mysql-libs-5.1.71-1.el6.x86_64 (rhel-6-server-rpms)
libmysqlclient.so.16()(64bit)
Available: mysql-libs-5.1.73-3.el6_5.x86_64 (rhel-6-server-rpms)
libmysqlclient.so.16()(64bit)

And installing MariaDB-compat does not help.

repoquery -ql on MariaDB-compat and mysql-libs leads me to think that maybe you should have both installed, but you can't because of this error.

Package mysql-libs-5.1.73-3.el6_5.x86_64 is obsoleted by MariaDB-shared-5.5.35-1.i386 which is already installed

I can't reproduce the problem described in the last comment (see output below – it's for 5.5.40, but 5.5.34 works as well).
But the last message from the comment "Package mysql-libs-5.1.73-3.el6_5.x86_64 is obsoleted by MariaDB-shared-5.5.35-1.i386 which is already installed" looks very suspicious, it seems the problem might have been in the mix of x86_64 / i386 packages.

# No *mariadb* or *mysql* packages are installed

$ rpm -qa | grep -i maria

$ rpm -qa | grep -i mysql

$

$ sudo yum install mytop

Loaded plugins: fastestmirror, refresh-packagekit, security

Loading mirror speeds from cached hostfile

 * base: mirror.awanti.com

 * epel: mirror.awanti.com

 * extras: mirror.awanti.com

 * updates: mirror.awanti.com

mariadb                                                                                      | 1.9 kB     00:00    

mariadb/primary_db                                                                           |  20 kB     00:00    

Setting up Install Process

Resolving Dependencies

--> Running transaction check

---> Package mytop.noarch 0:1.7-3.b737f60.el6 will be installed

--> Processing Dependency: perl(Term::ReadKey) >= 2.1 for package: mytop-1.7-3.b737f60.el6.noarch

--> Processing Dependency: perl(DBD::mysql) >= 1 for package: mytop-1.7-3.b737f60.el6.noarch

--> Processing Dependency: perl(Time::HiRes) for package: mytop-1.7-3.b737f60.el6.noarch

--> Running transaction check

---> Package perl-DBD-MySQL.x86_64 0:4.013-3.el6 will be installed

--> Processing Dependency: libmysqlclient.so.16(libmysqlclient_16)(64bit) for package: perl-DBD-MySQL-4.013-3.el6.x86_64

--> Processing Dependency: libmysqlclient.so.16()(64bit) for package: perl-DBD-MySQL-4.013-3.el6.x86_64

---> Package perl-TermReadKey.x86_64 0:2.30-13.el6 will be installed

---> Package perl-Time-HiRes.x86_64 4:1.9721-136.el6 will be installed

--> Running transaction check

---> Package MariaDB-compat.x86_64 0:5.5.40-1.el6 will be installed

--> Processing Dependency: MariaDB-common for package: MariaDB-compat-5.5.40-1.el6.x86_64

--> Running transaction check

---> Package MariaDB-common.x86_64 0:5.5.40-1.el6 will be installed

--> Finished Dependency Resolution

Dependencies Resolved

====================================================================================================================

 Package                        Arch                 Version                            Repository             Size

====================================================================================================================

Installing:

 mytop                          noarch               1.7-3.b737f60.el6                  epel                   32 k

Installing for dependencies:

 MariaDB-common                 x86_64               5.5.40-1.el6                       mariadb                23 k

 MariaDB-compat                 x86_64               5.5.40-1.el6                       mariadb               2.7 M

 perl-DBD-MySQL                 x86_64               4.013-3.el6                        base                  134 k

 perl-TermReadKey               x86_64               2.30-13.el6                        base                   31 k

 perl-Time-HiRes                x86_64               4:1.9721-136.el6                   base                   48 k

Transaction Summary

====================================================================================================================

Install       6 Package(s)

Total download size: 2.9 M

Installed size: 8.4 M

Is this ok [y/N]:

# All dependencies are resolved, mytop is satisfied with installing MariaDB-compat

The initial issue filed for 5.2 is likely to be still true, but since 5.2 / 5.3 versions are very old and not in a great demand, it makes no sense to fix them now.

For posterity it might be worth noting that in my case the issue was resolved by cleaning up yum repos. So now I only have official RHEL repos and EPEL, and mytop installs and there are no package issues.

It's possible that RPMforge was the cause of the troubles. RPMforge is largely abandoned and people should not use it.