Comment 2 for bug 857995

Hmnnn... Looking closer at the RPMs, they do obsolete mysql. I suspect the problem I ran into is I had the -enterprise-gpl versions installed (e.g. MySQL-client-enterprise-gpl.x86_64). For example:

MariaDB-shared-5.2.7-101.el5.x86_64 obsoletes mysql-shared
but
MySQL-shared-enterprise-gpl-5.0.72sp1-0.rhel5.x86_64 provides MySQL-shared

could the case difference cause a problem?

It could also be just a shortcoming of yum/rpm. In any case, I had to first remove the MySQL packages rather than having them removed automatically when installing MariaDB.

Thanks,
Jascha

On Nov 12, 2011, at 7:04 AM, Colin Charles wrote:

> Hi!
>
> We do provide the Obsoletes: tag in RPM. Where are you getting this
> from? mysql, mysql-server, etc. are obsoleted.
>
> Please provide where you got the RPM from and why yum didn't handle it.
>
> Thanks
>
> ** Tags added: packaging
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/857995
>
> Title:
> MariaDB packages don't obsolete MySQL rpms
>
> Status in Maria:
> New
>
> Bug description:
> Since the files contained in the MariaDB rpms conflict with those in
> the MySQL rpms, this should be reflected in the MariaDB spec files.
> This will enable yum to handle this at the package level, rather than
> find out when it tries to install the files.
>
> Ideally, each MariaDB package would "Obsolete" the corresponding MySQL
> package. This should allow the MariaDB package to be yum/rpm
> installed on a system with MySQL installed, with yum/rpm automatically
> removing the MySQL rpm.
>
> This is accomplished by adding an "Obsoletes : " tag to the rpm spec
> file and listing the package to be replaced in the same way as a
> "Requires :" tag.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maria/+bug/857995/+subscriptions