Comments - MariaDB versus MySQL - Compatibility

8 years, 5 months ago Elena Stepanova

Your concern is valid. Installing these packages would cause removal of MariaDB server.

Could you please specify which repository you use to install/upgrade MariaDB server? With Trusty, there are options -- MariaDB can be taken from the Ubuntu repo or from MariaDB repo. From what I see, currently Ubuntu repo contains MariaDB 5.5.39 and MySQL 5.5.40, which most likely causes the problem. MariaDB repo offers MariaDB 5.5.40 already.

But even with this version difference in the Ubuntu repo, it's not quite clear why the system forces you to install mysql* packages, could you please provide more details on how you got there? Was it a regular automatic system upgrade? Did you run apt-get install <something> and it attempted to pull mysql* as dependencies? Or was it something else?

Depending on which repo you use and which operation caused this, we'll try to suggest how to avoid it in future.

8 years, 5 months ago Robert Horgan

I am not sure whether I am pointing at the correct repositories, however here is my detail. Our first steps on Ubuntu install is to install webmin (perhaps this is where mysql imports are first initiated, I will ask a question on their support pages). Anyway after that is done and prior to any configuration we then install MariaDB. My commands are as follows:

apt-get install software-properties-common
apt-key adv --recv-keys --keyserver 0xcbcb082a1bb943db
add-apt-repository 'deb trusty main'
apt-get update
apt-get install mariadb-server

The list of further updates are later reported in webmin, but presumably as a result of an apt-get update script, not through any specific script on webmins part.
I will see if I can get comment from their support.
Is it possible that something could be done by MariaDB to protect its installation?
Thanks for your quick response.

8 years, 5 months ago Elena Stepanova

The whole thing is a bit mysterious, and I would really want to figure out what exactly is going on. Technically, you can have a similar problem during the period when MySQL 5.5.x is already in the Ubuntu repo, while MariaDB 5.5.x is not released yet. But it has not happened for a while, even for 5.5.40 -- MySQL 5.5.40 was uploaded to the Trusty repo on Oct 10, while MariaDB was released on Oct 9.

And even if you do catch the moment when the versions are different this way, apt-get upgrade just should not cause this effect. If it does, it might be a bug.

Still, assuming that somehow version mismatch is to blame, please refer to the KB page Version mismatch between MariaDB and Ubuntu/Debian Repositories. A few workarounds are described there, in your case the most suitable is probably Pinning the MariaDB repository. I cannot guarantee it will solve the problem for you, because as I said before, it's not quite clear what exactly causes it; but you can try, it shouldn't hurt.

If you have more information, please share it here or create an issue at our JIRA.

8 years, 5 months ago Robert Horgan

One thing which may be of relevance is that the installations were on Windows Azure and the Ubuntu was from the Windows Azure install. FWIW.

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.