Comment 8 for bug 521616

This still doesn't work correctly.
I have a server that had MariaDB 5.1.39 installed, back when the rpm's were still in /yum/CentOS
First of all, a yum update on that machine should have somehow alerted me that things were no longer functioning.

Second, after I changed my .repo file by hand to point to /yum/CentOS-MariaDB51 it still wasn't working. I had to also change my mirrors file.

Even after that, it wasn't working, since the package has been renamed to MariaDB-server (as opposed to the old MariaDB-OurDelta-server).

Now, I tried a yum install MariaDB-server, which should obsolete the old MariaDB-OurDelta-server. It seems that the obsoletion is the wrong way around though. Here's what I see:

# yum install MariaDB-server
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
 * addons: mirror.trouble-free.net
 * base: hpc.arc.georgetown.edu
 * extras: centos.mirror.nac.net
 * ourdelta: mirror.ourdelta.org
 * rpmforge: apt.sw.be
 * updates: mirror.trouble-free.net
480 packages excluded due to repository priority protections
Setting up Install Process
Package MariaDB-server is obsoleted by MariaDB-OurDelta-server, trying to install MariaDB-OurDelta-server-5.1.39-67.el5.x86_64 instead
Package MariaDB-OurDelta-server-5.1.39-67.el5.x86_64 already installed and latest version
Package MariaDB-server is obsoleted by MariaDB-OurDelta-server, trying to install MariaDB-OurDelta-server-5.1.39-67.el5.x86_64 instead
Package MariaDB-OurDelta-server-5.1.39-67.el5.x86_64 already installed and latest version
Nothing to do.

In short, a big mess. I think that this should be sorted properly, including alerting existing installs that they need to take action. Otherwise, we're going to have a bunch of outdated installations that will never be updated unless someone takes action. As such, I'm also increasing severity on this :)