Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-5252

Deb installation issues due to version mismatch between mariadb and ubuntu/debian repositories

        Details

        • Type: Bug
        • Status: Open
        • Priority: Major
        • Resolution: Unresolved
        • Affects Version/s: 5.5.33a
        • Fix Version/s: None
        • Component/s: None
        • Labels:

          Description

          This is an umbrella report for well-known deb package issues caused by the version mismatch with the official repositories.

          The problem was initially described in MDEV-3882, but later it was fixed after a part related to Wheezy specifics was fixed. However, the main problem still exists, as of 5.5.33a, it's described in the Knowledge base along with workarounds:

          https://mariadb.com/kb/en/installing-mariadb-deb-files/#version-mismatch-between-mariadb-and-ubuntudebian-repositories

          I don't want to reopen MDEV-3882 to keep the history consistent, so I'll link it to this report as a part of it, and will do the same with other ones that carry any new information. The rest will be closed as duplicates.

            Gliffy Diagrams

              Attachments

                Issue Links

                includes

                Bug - A problem which impairs or prevents the functions of the product. MDEV-3882 .deb upgrade from mysql to mariadb fails due to apt-get considering it a downgrade

                • Critical - Crashes, loss of data, severe memory leak.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. MDEV-5190 Packages not compatible with Ubuntu 13.04 due to mysql-common version difference

                • Major - Major loss of function.
                • Closed
                is duplicated by

                Bug - A problem which impairs or prevents the functions of the product. MDEV-5230 Ubuntu's Software Updater wants to uninstall MariaDB; then, cannot re-access the database.

                • Major - Major loss of function.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. MDEV-5276 Missing dependencies

                • Major - Major loss of function.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. MDEV-5301 Problem with installing from repository

                • Major - Major loss of function.
                • Closed
                is part of

                Task - A task that needs to be done. MDEV-6284 Merge downstream Debian/Ubuntu packaging into upstream MariaDB

                • Critical - Crashes, loss of data, severe memory leak.
                • Stalled
                relates to

                Bug - A problem which impairs or prevents the functions of the product. MDEV-5055 apt-get considers 5.5.33a downgrade from 5.5.33

                • Major - Major loss of function.
                • Closed

                Bug - A problem which impairs or prevents the functions of the product. MDEV-5557 New debian security upgrade break galera repo.

                • Major - Major loss of function.
                • Open

                  Activity

                  Ascending order - Click to sort in descending order
                  Hide
                  Permalink
                  mcoleman Matt Coleman added a comment -

                  I've submitted a pull request (https://code.launchpad.net/~mcoleman/maria/maria-fix-bug5190/+merge/194226) in LaunchPad to resolve this issue. The pull request resolves fresh installation of MariaDB; in order to resolve dependency issues with packages that explicitly depend on MySQL, I have created a new source package, maria-compat (https://code.launchpad.net/~mcoleman/maria/maria-compat), which creates libmysqlclient18, mysql-client, and mysql-server packages for a temporary workaround until one of the two permanent solutions (or both) is implemented:
                  1. work with the Debian/Ubuntu distribution maintainers and try to come up with a way to manage conflicting database engines, similar to (or maybe integrated into) the update-alternatives system
                  2. reach out to the projects that explicitly depend on MySQL packages and request that they update their dependencies for compatibility with MariaDB (ie. changing "Depends: libmysqlclient18" to "Depends: libmariadbclient18 | libmysqlclient18")

                  Show
                  mcoleman Matt Coleman added a comment - I've submitted a pull request ( https://code.launchpad.net/~mcoleman/maria/maria-fix-bug5190/+merge/194226 ) in LaunchPad to resolve this issue. The pull request resolves fresh installation of MariaDB; in order to resolve dependency issues with packages that explicitly depend on MySQL, I have created a new source package, maria-compat ( https://code.launchpad.net/~mcoleman/maria/maria-compat ), which creates libmysqlclient18, mysql-client, and mysql-server packages for a temporary workaround until one of the two permanent solutions (or both) is implemented: 1. work with the Debian/Ubuntu distribution maintainers and try to come up with a way to manage conflicting database engines, similar to (or maybe integrated into) the update-alternatives system 2. reach out to the projects that explicitly depend on MySQL packages and request that they update their dependencies for compatibility with MariaDB (ie. changing "Depends: libmysqlclient18" to "Depends: libmariadbclient18 | libmysqlclient18")
                  Hide
                  Permalink
                  tmarble Tom Marble added a comment -

                  I will look into this issue.. thank you very much for reporting it!

                  Obviously we want the user experience to be great on Debian and Ubuntu.

                  Show
                  tmarble Tom Marble added a comment - I will look into this issue.. thank you very much for reporting it! Obviously we want the user experience to be great on Debian and Ubuntu.
                  Hide
                  Permalink
                  ratzpo Rasmus Johansson added a comment -

                  Re-assigned to Otto

                  Show
                  ratzpo Rasmus Johansson added a comment - Re-assigned to Otto
                  Hide
                  Permalink
                  stefane Stefan Eriksson added a comment -

                  its a pretty serious issue and make me not want to use mariadb's repo in a production environment with replication. Its to much downtime if an apt-get upgrade would uninstall the master mysql server.

                  Show
                  stefane Stefan Eriksson added a comment - its a pretty serious issue and make me not want to use mariadb's repo in a production environment with replication. Its to much downtime if an apt-get upgrade would uninstall the master mysql server.
                  Hide
                  Permalink
                  otto Otto Kekäläinen added a comment - - edited

                  Matt Coleman and Stefan Eriksson : Work is in progress to make official Debian packages. There are lots of changes regarding the packaging and I expect that the issues here will be also solved as original libmysqlclient18 and new libmariadbclient18 will co-exsist properly in Debian main. Instead of update-alternatives we are using virtual package Provides "virtual-mysql".

                  Please take a look at https://wiki.debian.org/Teams/MySQL/MariaDBPlan

                  If you can help with testing, that would be great! Reports about official packaging can be sent to pkg-mysql-maint@lists.alioth.debian.org

                  I will close this issue once the packages hit Debian proper and/or the new contents of debian/* is merged to replace current bzr:mariadb-5.5/debian/*

                  Show
                  otto Otto Kekäläinen added a comment - - edited Matt Coleman and Stefan Eriksson : Work is in progress to make official Debian packages. There are lots of changes regarding the packaging and I expect that the issues here will be also solved as original libmysqlclient18 and new libmariadbclient18 will co-exsist properly in Debian main. Instead of update-alternatives we are using virtual package Provides "virtual-mysql". Please take a look at https://wiki.debian.org/Teams/MySQL/MariaDBPlan If you can help with testing, that would be great! Reports about official packaging can be sent to pkg-mysql-maint@lists.alioth.debian.org I will close this issue once the packages hit Debian proper and/or the new contents of debian/* is merged to replace current bzr:mariadb-5.5/debian/*

                    People

                    • Assignee:
                      otto Otto Kekäläinen
                      Reporter:
                      elenst Elena Stepanova
                    • Votes:
                      4 Vote for this issue
                      Watchers:
                      10 Start watching this issue

                      Dates

                      • Created:
                        Updated: