From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030718
Description of problem:
When doing a simple rpm -Uvh to MySQL 4.0, I get the following error:
libmysqlclient.so.10 is needed by (installed) mod_auth_mysql-20030510-3
libmysqlclient.so.10 is needed by (installed) perl-DBD-MySQL-2.9002-1
libmysqlclient.so.10 is needed by (installed) php-mysql-4.3.2-6
I'd like to be able to use 4.0's new features, and it's much easier to use RPM's
than to build from source.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Download MySQL-server from mysql.com and do a rpm -Uvh
Actual Results: Got error shown above
Expected Results: successful upgrade
At the moment, Red Hat does not support MySQL 4.0.x due to licensing
We did have MySQL 4.0 rpms available on Rawhide for a little while (before the
license problem was discovered). Along with the MySQL 4.0 rpms, we had a
mysqlclient10 rpm which contained the libmysqlclient.so.10 file (which is what
The MySQL folks are looking into the licensing issue and we'll roll the rpms
once the issue is taken care of.
*** Bug 108000 has been marked as a duplicate of this bug. ***
*** Bug 115640 has been marked as a duplicate of this bug. ***
Any news about this, maybe adding the mysql-4.x to fedora, since
fedora is a really gpl project, I read the mysql license and I don't
think should be any problems to add mysql 4 to Fedora Core, but in
the case of RedHat Enterprise applies the new mysql license, other
distros are using mysql-4..
*** Bug 136142 has been marked as a duplicate of this bug. ***
Despite "Resolution UPSTREAM" no relevant Bug found on:
Expected reasons are: MySQL-4.0 turned mysqclient license LGPL -> GPL.
Some proprietary code of RedHat Enterprise links against mysqlclient.
Fedora would be fine to use MySQL-4.x. It is just not viable for
RedHat to split Fedora vs. Enterprise development.
FYI Red Hat legal attitude at: Bug 136142
(mine): UPSTREAM points to the Red Hat legal department.
*** Bug 137296 has been marked as a duplicate of this bug. ***