MySQL Bugs: #13324: RHEL3 server RPM fails dependency on libmysqlclient.so.10

Bug #13324	RHEL3 server RPM fails dependency on libmysqlclient.so.10
Submitted:	19 Sep 2005 14:53	Modified:	19 Sep 2005 17:24
Reporter:	Roger Moffatt	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	4.1.14 RHEL3 rpm	OS:	Linux (linux RHEL3)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any

Description:
I've just done a fresh install of RedHat Enterprise Linux 3 onto a new server. I've downloaded the latest 4.1.14 RHEL3 RPMs from mysql.org but am unable to install.

The mysql client RPM installs OK, the server RPM fails with a missing dependency on libmysqlclient.so.10

Seems a bit fundamental...

Roger

How to repeat:
Install RHEL3 on (eg) a dell poweredge 750 and install the 4.1.14 RHEL3 server rpm

Verify if libmysqlclient.so.10 was installed with the RH install.

Having now re-installed the OS and DOWNGRADED to 4.0.26, it appears the same problem exists in the 4.0.26 RPMs. I should add that this is my first experience with RHEL3, previously I have used RH9 and installed mysql versions from 3.23 upto 4.1 with no problems. I have to move to RHEL3 now to support a 3rd party cluster application.

The problem seems to vary depending on which packages you install during the RHEL3 configuration, reducing the packages reduces the complaints. I guess it would do now that I think about it!

Yes, after running the GUI rpm installer (even though it doesn't complete) libmysqlclient.so.10 is actually present on the system at /usr/lib/mysql/libmysqlclient.so.10. If I run the installer again, it still has a problem saying unlocatable package libmysqlclient.so.10 required for perl-dbd-mysql

I'm going to try using a command line rpm install instead to see if I get more info.

Roger

Ah, OK. RTFM time

http://dev.mysql.com/doc/mysql/en/linux-rpm.html

However even *after* installing the shared libraries, I have the same problem. I note that the shared libraries are installed to /usr/lib whereas libmysqlclient.so.10 seems to be in /usr/lib/mysql ... not sure if that is the problem or not.

Drat! So near and yet so far!!

OK, after reading https://www.redhat.com/archives/fedora-list/2005-January/msg06942.html it appears I need the MYSQL-shared-compat rpm for RHEL3 - but it doesn't seem to be listed anywhere on the site. 

DAK where I can find it?

I can't believe I am the only person trying to install MySQL on RHEL3 so surely the documentation could do with a bit of an update and pref a link to a working set of RPM's? 

Ah, OK, more info. I just found this reference as well (just putting in stuff that might help others)

http://lists.mysql.com/mysql/187191

and the shared compatible libraries claim to be at this URL http://public.pdinc.us/rpms/mysql but I'm getting server not found errors.

Argggghhhh!!!
The whole problem seems to be related to the fact that the perl installation shipped with RHEL3 is linked? to libmysqlclient.so.10 for the dbd::mysql module which I'm guessing has been compiled in. Have I another way of attacking the problem??

Thanks for any help
Roger

Found a solution that at least seems to allow me to install.

http://mysql.mirrors.pair.com/Downloads/MySQL-4.1/MySQL-shared-compat-4.1.13-0.rhel3.i386....

It IS on the mysql site - hidden away.

Is this safe to use? 

Roger

I am changing the status to not a bug since it is an issue OS->MySQL rpm install.
For to avoid this problem during the OS install I deselect the MySQL options
if I intend to install another version than shipped with the OS.
Regarding to your last question, sorry I don't have any experience with that
install procedure.

Hi Miguel

I'm sorry but I have to take issue with your closing comment. RHEL3 was installed WITHOUT ANY MySQL option selected and so I had a completely fresh system on which to install MySQL 4.1. That is therefore NOT a correct workaround.

I think this needs a real solution - either by way of correcting the documentation or making the compatibility libraries part of the main RPM package. At the very least they should be downloadable from the MySQL web site along with the main RPMs. They simply aren't visible enough and from my web searches, plenty of other people are coming up against this problem and moaning about finding a solution. Hundreds of man hours are being wasted due to faulty documentation and I don't think that's a great advert for MySQL.

Also, be aware that there appears to be no way to install RHEL3 without encountering this problem since as soon as you select the development package, you are forced to install perl-dbd-mysql which is causing the dependency failure. 

Hope that clarifies why I think it needs some action.

Roger

As for DBD::mysql, I cannot say how redhat packages it in their RPM. I can say that DBD::mysql, if you build it from the latest sources, should give you no problems. The problem with that is some people really want to use only RPMs. The thing with RPMs is that you have to make sure that all your dependencies are satisfied, and any change, variation outside of how a distribution that has a given set of RPMs that comprise it's completeness can result in something not working.

Also, if you're going to use a different mysql server RPM than was installed, I would recommend removing the rpm for the DBD::mysql perl module that came installed with RH, because it obviously won't work with another version of the mysql client libs. Then, after you have the new version of DBD::mysql running, use CPAN to get the latest DBD::mysql and compile and install that way.

"after you have the latest version of DBD::mysql" I meant "after you have the latest MySQL server"...