Details
Major
Description
Sometimes we get complaints on IRC about MariaDB-Galera being installed instead of MariaDB-server. I think we don't have a report about it yet because we could not reproduce it. I have a guess about the reason.
Right now I'm getting the same behavior trying to install from MariaDB 5.5 repo.
On CentOS, it happens when I run
sudo yum install mysql-server
literally, with lower-case mysql-server.
On Fedora, it happens when I run
sudo yum install mariadb-server
again, literally, with lower-case mariadb-server.
In both cases, MariaDB-Galera-server 5.5.36 is installed.
Looking at cpack_rpm.cmake, I see that mysql-server is defined as an alternative name for both MariaDB-server and MariaDB-Galera-server; same for mariadb-server, only it is defined conditionally on Fedora.
So, my guess is when an alternative name is used in yum install command, and there are several packages which have this alternative name and the same version, then the choice is indeterministic (or maybe it depends on some non-obvious factors).
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Oden Eriksson, what do you think about this?
I'll have a look the 21:st.
It doesn't look like the "shorter wins" here. Both MariaDB-server and MariaDB-Galera-server provide (and obsolete?) mysql-server and mariadb-server. They also conflict with each other. So when a mariadb-server or mysql-server are requested, yum has a choice. May be it uses the longer name, may be the decision rule is not specified. Either way, apparently it choses MariaDB-Galera-server, at least sometimes.
I don't know if we can fix that at all in 5.5 or 10.0. In 10.1 MariaDB-Galera-server does not exist, so the issue disappears.
MariaDB-Galera-server "obsoletes" mysql-server and mariadb-server so yum installs it instead. This obsoletes should probably be removed.
If 2 packages provide the same name and version the package with the shorter name wins, which is what we want here.