The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-21. For the latest, interactive version please visit https://mariadb.com/kb/.

MariaDB 5.5.33 Debian and Ubuntu Installation Issues

Shortly after the MariaDB 5.5.33 release we became aware of some installation issues with the Debian and Ubuntu repositories. These issues were fixed in MariaDB 5.5.33a, but due to how apt works, steps need to be taken to solve the broken dependencies before upgrading.

We know of three scenarios when dependencies were broken. The steps to fix each of them are pretty much the same, only the list of broken dependencies and hence the list of packages to take care of them differs. The basic idea is to downgrade those certain packages to 5.5.32 temporarily before upgrading them to 5.5.33a.

If you ran into issues when moving from MariaDB 5.5.32 to MariaDB 5.5.33, look through each of the three scenarios to see which one applies to you and then follow the steps to apply that fix.

Contents

  1. Applying the fix
  2. 5.5.32 server + 5.5.32 client upgraded to the initial (17 Sep 2013) release of 5.5.33
  3. 5.5.32 Galera server and 5.5.32 MariaDB client upgraded to 5.5.33
  4. 5.3.12 server + 5.3.12 client + 5.5.32 libmariadbclient18 upgraded to 5.5.33

Applying the fix

To get your system ready to apply the fix, do the following:

  • Comment out the standard MariaDB 5.5 repo in the /etc/apt/sources.list or /etc/apt/sources.list.d/mariadb.repo file (or wherever you have the repositories configured).
  • Add a MariaDB 5.5.32 repository to the sources.list. The easiest way is to add the following. Just replace '{os}' and '{dist}' with the appropriate values. 
deb http://ftp.osuosl.org/pub/mariadb/mariadb-5.5.32/repo/{os} {dist} main

For example, on Debian Wheezy the line would be:

deb http://ftp.osuosl.org/pub/mariadb/mariadb-5.5.32/repo/debian wheezy main

And on Ubuntu Raring the line would be:

deb http://ftp.osuosl.org/pub/mariadb/mariadb-5.5.32/repo/ubuntu raring main
  • Then run 'sudo apt-get update'
  • Then 'sudo apt-get install' the list of packages to downgrade as given in the applicable section below.
  • Next, modify our sources.list to remove the 5.5.32 repo and switch back to the normal 5.5 repo
  • Then 'sudo apt-get update' to get things back to normal
  • As a final optional step, once your normal mirror has at least MariaDB 5.5.33a you can 'sudo apt-get upgrade' to upgrade. To check what version of MariaDB our mirror has, run the following command (after running 'sudo apt-get update'): 
apt-cache show mariadb-server | grep Version

5.5.32 server + 5.5.32 client upgraded to the initial (17 Sep 2013) release of 5.5.33

In this first scenario, both client and server were partially upgraded to 5.5.33 before the process aborted. The problem looks like this:

You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
 libmariadbclient18 : Depends: libmysqlclient18 (= 5.5.32+maria-1~wheezy) but 5.5.33+maria-1~wheezy is installed
 libmysqlclient18 : Depends: libmariadbclient18 (= 5.5.33+maria-1~wheezy) but 5.5.32+maria-1~wheezy is installed
 mariadb-client-5.5 : Depends: libmariadbclient18 (>= 5.5.33+maria-1~wheezy) but 5.5.32+maria-1~wheezy is installed
 mariadb-client-core-5.5 : Depends: libmariadbclient18 (>= 5.5.33+maria-1~wheezy) but 5.5.32+maria-1~wheezy is installed
 mariadb-server : Depends: mariadb-server-5.5 (= 5.5.33+maria-1~wheezy) but 5.5.32+maria-1~wheezy is installed
 mariadb-server-core-5.5 : Depends: libmariadbclient18 (>= 5.5.33+maria-1~wheezy) but 5.5.32+maria-1~wheezy is installed

To fix it, the following server and client packages need to be temporarily downgraded to 5.5.32 (replace 'wheezy' with the name of whatever distribution you are using):

sudo apt-get install \
  libmysqlclient18=5.5.32+maria-1~wheezy \
  mariadb-client-5.5=5.5.32+maria-1~wheezy \
  mariadb-client-core-5.5=5.5.32+maria-1~wheezy \
  mariadb-server=5.5.32+maria-1~wheezy \
  mariadb-server-core-5.5=5.5.32+maria-1~wheezy

5.5.32 Galera server and 5.5.32 MariaDB client upgraded to 5.5.33

In this scenario, the client upgraded, but Galera-server did not. The problem looks like this:

The following packages have unmet dependencies:
 libmariadbclient18 : Depends: libmysqlclient18 (= 5.5.32+maria-1~wheezy) but 5.5.33+maria-1~wheezy is installed
 libmysqlclient18 : Depends: libmariadbclient18 (= 5.5.33+maria-1~wheezy) but 5.5.32+maria-1~wheezy is installed
 mariadb-client-5.5 : Depends: libmariadbclient18 (>= 5.5.33+maria-1~wheezy) but 5.5.32+maria-1~wheezy is installed
 mariadb-client-core-5.5 : Depends: libmariadbclient18 (>= 5.5.33+maria-1~wheezy) but 5.5.32+maria-1~wheezy is installed

To fix it, only the client packages need to be temporarily downgraded to 5.5.32 (replace wheezy with whatever your distribution is):

sudo apt-get install \
  libmysqlclient18=5.5.32+maria-1~wheezy \
  mariadb-client-5.5=5.5.32+maria-1~wheezy \
  mariadb-client-core-5.5=5.5.32+maria-1~wheezy

5.3.12 server + 5.3.12 client + 5.5.32 libmariadbclient18 upgraded to 5.5.33

In this scenario, only the library upgraded. The problem looks like this:

The following packages have unmet dependencies:
  libmariadbclient18: Depends: libmysqlclient18 (= 5.5.32+maria-1~lucid) but 5.5.33+maria-1~lucid is installed
  libmysqlclient18: Depends: libmariadbclient18 (= 5.5.33+maria-1~lucid) but 5.5.32+maria-1~lucid is installed

To fix it, the library needs to be downgraded to 5.5.32 (replace wheezy with your distribution):

sudo apt-get install \
  libmysqlclient=5.5.32+maria-1~wheezy \
  libmariadbclient=5.5.32+maria-1~wheezy

After switching back to the 5.5 repo, the libraries won't get upgraded, they will stay 5.5.32 until you upgrade the server to 5.5.33a.

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.