upgrading Mariadb 10.3 to 10.5 and more...

[Jeff63]

Hello ^^)

I have a very old server (2003) that need to be replaced. it runs suse linux.

The new server is based on Debian 10.10, so I encounters a lot of differences in the configurations files and in software versions...

this question is about MariaDB, on old server its version is :
'mariadb Ver 15.1 Distrib 10.4.17-MariaDB, for Linux (x86_64) using EditLine wrapper'

on Debian 10 it's :
'mariadb Ver 15.1 Distrib 10.3.29-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2'

I've digged the net and seen v10.4 have some more stuff and security patches than the actual debian 10.10 version.

so, if I want to migrate the (lotsa !) databases from the old suse server to the new debian one I need first to upgrade mariadb to at least the same version or better.

I haven't found mariadb v10.4 in the debian repos, there is a v10.5 in testing one, so the question : is it safe to upgrade my debian 10.10 mariadb v10.3 stable version by that testing v10.5 ? is it mature enough ?

or should I go to Mariadb own website and download/install their new version (currently v10.6.3 for Debian buster)

what is the right thing to do for a production server ? (personaly I would go for v10.6.3)

next am I forced tu use the same EditLine wrapper than on the suse server for the imported databases to work as it was before ? (somewhat noob question I know )

Thanks for the help ^^)
Jeff

[stevepusser]

I haven't found mariadb v10.4 in the debian repos, there is a v10.5 in testing one, so the question : is it safe to upgrade my debian 10.10 mariadb v10.3 stable version by that testing v10.5 ? is it mature enough ?

I think we have an XY problem here, the 10.3 series is constantly updated in Stable, so those security issues don't exist.

Code: Select all

mariadb-10.3 (1:10.3.29-0+deb10u1) buster; urgency=medium

  [ Otto Kekäläinen ]
  * SECURITY UPDATE: New upstream version 10.3.29. Includes fixes for the
    following security vulnerabilities:
    - CVE-2021-2154
    - CVE-2021-2166
  * Previous release 10.3.28 included fixes for:
    - CVE-2021-27928
  * Remove patch regarding a test now removed by upstream (MDEV-22653).
  * Remove obsolete sql file removed by upstream (MDEV-24586).
  * Update symbols to include new one from MariaDB Client 3.1.13
  * Innotop: Add support for MariaDB 10.3 (Closes: #941986)
  * Upstream release includes fix for MDEV-24194: "Invalid syntax errors on
    syntax WHERE `field` IS NULL = 0" (Closes: #977383)

  [ Daniel Black ]
  * Add caching_sha2_password.so (Closes: #962597)

 -- Otto Kekäläinen <otto@debian.org>  Sun, 09 May 2021 20:06:52 -0700

mariadb-10.3 (1:10.3.27-0+deb10u1) buster; urgency=medium

  * New upstream version 10.3.27. Includes fixes to serious regressions in
    MariaDB 10.3.26 that corrupted data or made server unable to start.
  * SECURITY UPDATE: Includes new upstream 10.3.26 which included fixes for
    the following security vulnerabilities:
    - CVE-2020-28912
    - CVE-2020-14812
    - CVE-2020-14789
    - CVE-2020-14776
    - CVE-2020-14765
    - CVE-2021-2194
  * Upstream 10.3.26 included:
    - Fix mytop shebang (Closes: #972780, Closes: #970681)
  * Remove 3 patches applied upstream.

 -- Otto Kekäläinen <otto@debian.org>  Wed, 25 Nov 2020 11:50:19 +0200

mariadb-10.3 (1:10.3.25-0+deb10u1) buster-security; urgency=high

  * SECURITY UPDATE: New upstream version 10.3.25. Includes fixes for the
    following security vulnerabilities:
    - CVE-2020-15180
  * Salsa-CI: Update to be compatible with latest master/salsa-ci.yml

 -- Otto Kekäläinen <otto@debian.org>  Mon, 12 Oct 2020 20:46:30 +0300

mariadb-10.3 (1:10.3.23-0+deb10u1) buster; urgency=high

  * SECURITY UPDATE: New upstream version 10.3.23. Includes fixes for the
    following security vulnerabilities (Closes: #961849):
    - CVE-2020-2752
    - CVE-2020-2760
    - CVE-2020-2812
    - CVE-2020-2814
    - CVE-2020-13249
  * Backport upstream patch to fix regression in RocksDB ZSTD detection
    which prevents a serious bug and also autopkgtest detectable
    regression.
  * Update libmariadb symbols for upstream release 3.1.8. Upstream
    added one new symbol and it needs to be tracked in the symbols file.

 -- Otto Kekäläinen <otto@debian.org>  Sat, 04 Jul 2020 15:31:51 +0300

You also need to read this in the Debian wiki: https://wiki.debian.org/DontBreakDebian

tl;dr: Just adding the testing repo to stable and trying to install packages from upstream almost always leads to a broken Debian install.

If you did really really need a newer version, the safest way is to install a backported version, either from Debian backports, one that someone else has done, or do it yourself. I would be be very cautious about doing one, though, since it's a package that many others depend upon. I think that Debian has worked around that by having each version in a separate package, such as mariadb-10.3, mariadb-10.5, and so on, which allows them all to be installed at the same time.

[Jeff63]

Hello ^^)
Thanks for the answer, btw my problem is that all the databases on the old server where created with a newer version of mariadb than we have on Debian.

There is a lot of new mariadb fields / functions in it that aren't existing in our debian version 10.3 yet.

please have a look here : https://mariadb.com/kb/en/upgrading-fro ... riadb-104/ especially in the 'incompatibles changes' section, you can see for v10.4 to v10.5 too.

hence the question, I don't want to break the -important- databases I have to migrate from mariadb v10.4 on suse linux to the new server under debian 10 with 'only' mariadb v10.3...

If I end up with non/partly working databases after migrating I will be very very embarassed...

so what must be done for guaranteed working migration and safety of that databases ?

I don't think downgrading mariadb versions will be safe for databases...

[dilberts_left_nut]

so what must be done for guaranteed working migration and safety of that databases ?

Plenty of testing.

[stevepusser]

I took a look at the debianized source for 10.5, and it breaks a lot of the 10.3 packages, so you can't have both, and may break all of Buster.

I would suggest upgrading that system now to Debian 11 "Bullseye", which should be released in a week or two. Then you'll have 10.5.

Or wait for Debian 11 to be released and then upgrade, just to be safe. And of course, backups, backups, backups.

[Jeff63]

Hello stevepusser ^^)

I'm still at determining what's will broke when migrated from old suse to debian 10 and how to prevent it,
so the new server is far for 'production ready' yet

Think I'll try the "bullseye" path as I don't have too much time to wait the new version to be published... and need to continue to migrate things (I still have a lotsa stuff to move to that new server, titan's work ! ^^)

Thanks for the advice ^^)

last question : they produce debbian 10 packages of all their MariaDB stuff at MariaDB.com, is it this you had a look at or debian's own ?
would be curious to know what differences it could have between the two...

[stevepusser]

I have no idea, to be honest. If in doubt, stick with the Debian packages. I suppose one could cross their fingers and ask at mariadb.com.