MySQL Bugs: #6342: Backward-compatibility

Bug #6342	Backward-compatibility
Submitted:	31 Oct 2004 11:22	Modified:	13 Jan 2005 12:12
Reporter:	Peter Grotz	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Packaging	Severity:	S3 (Non-critical)
Version:	4.1.7	OS:	Linux (SuSE-Linux 9.1)
Assigned to:	Lenz Grimmer	CPU Architecture:	Any

Description:
in package MySQL-shared-compat , which includes the shared libraries for backward compatibility libmysqlclient.so.12 is not included. theres is no compatibility to 4.0.22-clients.

How to repeat:
trying to connect with 4.0.22-clients -> no connection

This problem seems to be stoping me from upgrading MySQL to the last version (RedHat Linux 
9).

I have Postfix compiled with MySQL 4.0.16-0 (MySQL-shared-compat-4.0.16-0), using 
libmysqlclient.so.12.

I can't upgrade to the last version of MySQL because I'll break dependencies with Postfix.

I can't compile a new Postfix using a new libmysqlclient because I can't install the new MySQL!

hi
same here - I'm trying to upgrade too:
rpm -Uvh MySQL-shared-compat-4.1.7-0.i386.rpm

though this is on fedora core 1 but the postfix-dependency catches me too:
error: Failed dependencies:
        libmysqlclient.so.12 is needed by (installed) postfix-2.1.5-3.MySQL.sasl1.tls.vda.fc1.i386

please notify me somehow when this is/will be fixed.
regards
harald kapper

hi
current mysql-shared-compat.rpm (v4.1.8) still shows the same problem as 4.1.7

will we get any fix here?

[miguel@light ~]$ rpm -qpl MySQL-shared-compat-4.1.8-0.i386.rpm
warning: MySQL-shared-compat-4.1.8-0.i386.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5
/usr/lib/libmysqlclient.so
/usr/lib/libmysqlclient.so.10
/usr/lib/libmysqlclient.so.10.0.0
/usr/lib/libmysqlclient.so.14
/usr/lib/libmysqlclient.so.14.0.0
/usr/lib/libmysqlclient_r.so
/usr/lib/libmysqlclient_r.so.10
/usr/lib/libmysqlclient_r.so.10.0.0
/usr/lib/libmysqlclient_r.so.14
/usr/lib/libmysqlclient_r.so.14.0.0
[miguel@light ~]$

Sorry, I have no answers ...just some questions... I need some direction which I believe some of you may be able to provide...

I would like to use a secure linux distribution that is capable of running latest MySQL...for the purposes building a user subscription and reporting system...  this is early in the testing phase.   My initial choice was RH Fedora Core 3 but see all these upgrade issues....  found http://fedoranews.org/contributors/tony_smith/mysql/  which I haven't tried yet.  I am relatively new to the RPM packaging but know enough unix to piece it together given correct instructions :-) ....   I've installed a recent 4.1 version of MySQL on Solaris based on the docs...  So with this in mind, should I stick to Fedora and follow the instructions on the link above?  If not, is there an easier way?  I thought I'd just uninstall mysql 3.23 and install the newest rpm which will prompt me for the dependencies which I'll have to get... doesn't sound that it's that simple... Do I need to use RPMs in RH ... remember my objectives...   and I'm doing this as a learning exercise.

Thanks for any feedback and if there's a better forum you can point me to...

I believe my efforts are DB centric and thus have chosen to look here...

Darko

Ok, after a bit more searching... found comments here:
http://dev.mysql.com/doc/mysql/en/Upgrading-from-3.23.html

from user Gustavo that seem promising :
----------
Posted by Gustavo on October 19 2004 2:04pm [Delete] [Edit] 

We've recently upgraded from 3.23 to 4.0.21.

We have more than 1200 different databases on the server with 12GB of data. Clients spread around 10 computers connect to this server. Everything was really easy and we had no problems at all.

We just had to
/etc/init.d/mysql stop
rpm -Uvh MySQL-server-4.0.21-0.i386.rpm
rpm -Uvh MySQL-devel-4.0.21-0.i386.rpm
rpm -Uvh MySQL-client-4.0.21-0.i386.rpm
/etc/init.d/mysql start

---------------

I certainly can do that if this is true ...   comments ???

This is actually not a problem, if one simply installs the needed
rpm packages despite the warning from rpm. By using switches -i --force
for rpm, one can install shared libraries from both 4.0.x and 4.1.x.

I think this is a limitation of the rpm itself, not allowing by default to
have several packages installed in parallel. It does allow it, but requires
--force. One can later on use rpm -q -f <filename> to check to which rpm
package a file belongs to.

I have sent a mail to our packaging team to consider making a shared
library rpm which includes all shared library versions in one package. In
practise this is same as installing all the current ones using --force.

Reopened and re-assigned - trying to fix this for the 4.1.9 shared-compat RPM...

I've updated the MySQL-shared-compat.spec file in the 4.1 tree - the upcoming 4.1.9 release will include a fixed package as well:

ChangeSet@1.2220, 2005-01-13 13:07:35+01:00, lenz@mysql.com
  - added the 4.0 shared mysqlclient libraries to the 4.1 "shared-compat" RPM

(Fix will be merged and updated for 5.0 as well to include the 4.1 libs)

we ran across this too, here is our solution rpm

http://public.pdinc.us/rpms/mysql