I see that Fedora 44 will update MariaDB from 10.5 to 11.8.
What could I do to update my current Fedora 43 installation from 10.5 to 11.8 before upgrading to Fedora 44 so that I can make sure my db is running properly on 11.8 first before upgrading the entire OS? Fedora updates have gone very smoothly for the last several years, but I would just like to get that particular concern out of the way while I have some free time before F44 is released.
Check specifically online for changes that will occur in mariadb with the version upgrade and for instructions on how to proceed.
A simple google search for upgrade mariadb 10.5 to 11.8 gives a lot of results for instructions. Example:
I do not use mariadb, but there have often been changes in database versions that break the existing installations when a major version upgrade occurs.
Be sure to back up before you proceed:
sudo dnf swap mariadb-server mariadb11.8-server
I was not able to change versions using dnf swap, that resulted in too many packages being removed.
I also tried installing all of the associated mariadb11.8 packages by installing mariadb11.8 and mariadb11.8-* with the --allowerasing option, and that seemed that it would result in all the mariadb server packages being installed, but would result in mythtv packages being removed.
I’ve done some delayed cleanup and backup of the database that I should have done previously anyway, so I think I will just wait for the new F44 mariadb packages what will presumably be setup in a way that they can directly replace the current F43 versions.
It seems you have mythtv installed. That appears to come from rpmfusion-free so it would be relatively simple to allow it to be removed then reinstall it after updating the mariadb packages.
If you cannot perform the upgrade of mariadb while still on f43 it will probably be much more difficult to do so while attempting to upgrade fedora to f44.
I suggest you work out the stumbling blocks now for mariadb instead of fighting both the f44 upgrade and the db version update at the same time.
That does sound like a good approach. I am a little worried that the RPM file “provides” fields are not setup correctly in the mariadb11.8 packages, because I was not expecting db client applications to get marked as not having needed packages and removed, I expected that the 11.8 packages could be a drop in replacement for the 10.16 packages.
I say applications because mythtv is what I care about, but the akonadi-server-mysql package will be removed as well when swapping mariadb11.8 for the current mariadb installation. The akonadi-server-mysql is from the main Fedora repository, so that doesn’t lead me to believe it is just a mistake in the “requires” field of the rpmfusion packages.
I guess I will just have to make sure my configuration files are backed up and just try reinstalling the myth packages after swapping the database server versions.
There were a few additional stumbling blocks. The most noticeable for me is akonadi-server-mysql because I use kmail, and kmail cannot retrieve the account information it needs without akonadi-server-mysql, and that package cannot be installed because it requires mariadb, but mariadb11.8 provides the capability mariadb-any.
I filed a bugzilla ticket, and the Fedora packager realized that exposed a mistake in the recommendations for packages which need database. It seems that the packages should have been requiring mariadb-any and recommending mariadb, because mariadb points to the default package, and mariadb-any will match alternate older or newer versions.
For details see 2456347 – mariadb11.8 provides capability mariadb-any but not capability mariadb, so packages needing mysql or mariadb do not accept mariadb11.8 as a valid server
2 Likes