MySQL Bugs: #20112: Problems with 5.0.22 install

Bug #20112	Problems with 5.0.22 install
Submitted:	28 May 2006 14:53	Modified:	5 Jun 2006 15:25
Reporter:	Peter Laursen (Basic Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S2 (Serious)
Version:	5.0.22	OS:	Linux (SuSE Linux 10.0)
Assigned to:		CPU Architecture:	Any

Description:
I tried to install

* the server binary
* the shared library
* the 'mysql' client binary

of the glibc23 RPM 'package set'.  I am using the SuSE/KDE/Yast2 interface. I have never had any issue with installation of any other MySQL 4.1.x, 5.0.x or 5.1.x before.  Everything has installed with no error messages.  But with this set, I experience

* the server binary installs OK
* the shared libray displays a dependy conflict that no versions did before.  The interface offers me an option not to set the existing version (5.0.21) as 'protected'.  After choosing that it installs.  But this is a new thing.  This dependency conflict was not seen before,
* The client binary does not install at all.  After the dependency check it does not display/find any installable package and after pressing 'OK' nothing is installed.

I have recently (2-3 days) ago updated the Linux kernel from SuSE 'Online Update'.  Is that part of the problem?

How to repeat:
Install the MySQL 5.0.22 glibc23 RPM 'set of packages' as above on a fully updated SuSE 10.0 Linux system.

Suggested fix:
first .. find out what is going on!?
A packaging error?
An issue with the new Linux kernel?

I do not know what additional information I could provide, so please ask!

The exact file names are
* MySQL-server-5.0.22-0.glibc23.i386.rpm
* MySQL-shared-5.0.22-0.glibc23.i386.rpm
* MySQL-client-5.0.22-0.glibc23.i386.rpm

.. as they have become available from the FTP-mirror, that I normally use  (Sun - Denmark), this morning.

Also after uninstalling the 5.0.21 client package the 5.0.22 RPM version of the client package does not install anything.

Thank you for a problem report. Please, send the results of:

rpm -q -a | grep -i mysql

command. 

Note, that version 5.0.22 is not yet released officially.

I know it is not official yet.  But nevertheless available form offical MySQL FTP-mirrors!  Somebody has to be the first to break his neck with this :-)

Returns of 
rpm -q -a | grep -i mysql

With 5.0.21 installed
metusalinux:~ # rpm -q -a | grep -i mysql
mysql-connector-odbc-3.51.12-1
mysql-workbench-1.0.6beta-1
MySQL-client-5.0.21-0
mysql-administrator-1.1.10-1
php4-mysql-4.4.0-6
apache2-mod_auth_mysql-2.8.1-5
MySQL-server-5.0.21-0
php5-mysqli-5.0.4-9
MySQL-Max-5.0.21-0
perl-DBD-mysql-3.0002-2
MySQL-shared-compat-5.0.21-0
qt3-mysql-3.3.4-28
mysql-connector-java-3.1.8-3
mysql-query-browser-1.1.12-2
rekall-mysql-2.2.1-11
postfix-mysql-2.2.5-5
php5-mysql-5.0.4-9
metusalinux:~ #

After install of standard server and max server (they both intall with no error messages)
metusalinux:~ # rpm -q -a | grep -i mysql
mysql-connector-odbc-3.51.12-1
mysql-workbench-1.0.6beta-1
MySQL-client-5.0.21-0
mysql-administrator-1.1.10-1
php4-mysql-4.4.0-6
apache2-mod_auth_mysql-2.8.1-5
php5-mysqli-5.0.4-9
MySQL-server-5.0.22-0.glibc23
perl-DBD-mysql-3.0002-2
MySQL-shared-compat-5.0.21-0
MySQL-Max-5.0.22-0
qt3-mysql-3.3.4-28
mysql-connector-java-3.1.8-3
mysql-query-browser-1.1.12-2
rekall-mysql-2.2.1-11
postfix-mysql-2.2.5-5
php5-mysql-5.0.4-9
metusalinux:~ #

Next when trying to install shared libray I got the error message that existing 5.0.21 was protected.  I uninstalled it using Yast2 'Software Management' (and when doing so Yast2 installed the one originally shipped with the distribution to solve dependencies) and after that the 5.0.22 shared libray installed.  After that:
metusalinux:~ # rpm -q -a | grep -i mysql
mysql-connector-odbc-3.51.12-1
mysql-workbench-1.0.6beta-1
MySQL-client-5.0.21-0
mysql-administrator-1.1.10-1
php4-mysql-4.4.0-6
apache2-mod_auth_mysql-2.8.1-5
mysql-shared-4.1.13-3
php5-mysqli-5.0.4-9
MySQL-server-5.0.22-0.glibc23
perl-DBD-mysql-3.0002-2
MySQL-Max-5.0.22-0
MySQL-shared-5.0.22-0.glibc23
qt3-mysql-3.3.4-28
mysql-connector-java-3.1.8-3
mysql-query-browser-1.1.12-2
rekall-mysql-2.2.1-11
postfix-mysql-2.2.5-5
php5-mysql-5.0.4-9
metusalinux:~ #

Now clicking the client RPM pacckage Yast2 did not show any binaries in the package to install
After choosing to install <nothing> :-) Yast2 just closes down (nothing to do). And of course it still results in:
metusalinux:~ # rpm -q -a | grep -i mysql
mysql-connector-odbc-3.51.12-1
mysql-workbench-1.0.6beta-1
MySQL-client-5.0.21-0
mysql-administrator-1.1.10-1
php4-mysql-4.4.0-6
apache2-mod_auth_mysql-2.8.1-5
mysql-shared-4.1.13-3
php5-mysqli-5.0.4-9
MySQL-server-5.0.22-0.glibc23
perl-DBD-mysql-3.0002-2
MySQL-Max-5.0.22-0
MySQL-shared-5.0.22-0.glibc23
qt3-mysql-3.3.4-28
mysql-connector-java-3.1.8-3
mysql-query-browser-1.1.12-2
rekall-mysql-2.2.1-11
postfix-mysql-2.2.5-5
php5-mysql-5.0.4-9
metusalinux:~ #

Two problems:

1) Yast2 demands share library 5.0.21 to be uninstalled before 5.0.22 can be installed.  It is a minor issue - but was never the case before

2) Nothing  installable is found in the client package

@Valeriy

Why doesn't this report show up with a search?
Not matter how I search it does not show up!

It is officially released now. Please, check size/date/MD5 checksum for the files you downloaded. If they are not the same as current, please, download again, check installation and inform about the results.

Try to search for this report now.

Sorry .. but I was away for the weekend.

1) The search is OK now.
2) This PC is 'stand-in' for a server (that is being upgraded) at this moment, so I may take a day of two before I can test the new RPMs.  But there are new ones available (dated May31th) I see.

OK .. server update finished now, actually, so I can try this.
Everything installed without problems with the new files.

Closed as problem is not repeatable with newer binaries of 5.0.22, after official release.