F44 Change Proposal: switch distribution default MariaDB from 10.11 to 11.8 [SelfContained]

switch distribution default MariaDB from 10.11 to 11.8

Wiki

Announced

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Summary :open_book:

MariaDB is packages now use the versioned package layout.

Currently we have packages mariadb10.11 and mariadb11.8 which both provides their respective versioned named sub-packages (e.g. mariadb10.11-server or mariadb11.8-errmsg etc.)

A “distribution default” version is the one, that also provides the unversioned names (e.g. mariadb-server or mariadb-errmsg etc.), making it easy for user to discover, install, and for other packages to depend on.

Currently the “distribution default” version of MariaDB is 10.11. Let’s switch to 11.8.

Owner :open_book:

Detailed Description :open_book:

The technical implementation is by a ON/OFF macro in the MariaDB packages SPECfiles.

There can’t be two same “distribution default” packages at the same time, since they would create conflicts. So the switch must be done simultaneously.

Similar change was done for [[Changes/switch_distribution_default_MySQL_from_8.0_to_8.4|MySQL in F43]] and went well.

No issues expected.

Feedback :open_book:

 

Benefit to Fedora :open_book:

MariaDB 11.8 is the latest LTS version of MariaDB.

Scope :open_book:

  • Proposal owners:
    ** will do switch in the packages mariadb10.11 and mariadb11.8
    ** will check for any issues with the dependent packages
  • Other developers:
    ** are expected to cooperate in case of fixes in dependent packages are needed
  • Release engineering: N/A (not needed for this Change)
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with the Fedora Strategy: Fedora leads in the Linux distribution development

Upgrade/compatibility impact :open_book:

DB administrators need to handle the DB upgrade, as usual.

In case the DB admin need more time with the old MariaDB 10.11, is still will be available as an alternative in Fedora 44.

Early Testing (Optional) :open_book:

N/A

How To Test :open_book:

TBA once the change is implemented

User Experience :open_book:

Load of features and enhancements inside of the software itself.

Dependencies :open_book:

amarok - will need to be rebuilt against the new mariadb-devel

zoneminder - will need to be rebuilt against the new mariadb-devel

Contingency Plan :open_book:

  • Contingency mechanism: The change will be reverted.
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? No

Documentation :open_book:

Release Notes :open_book:

\n

Last edited by @alking 2026-01-13T16:24:46Z

Last edited by @alking 2026-01-13T16:24:46Z

How do you feel about the proposal as written?

  • Strongly in favor
  • In favor, with reservations
  • Neutral
  • Opposed, but could be convinced
  • Strongly opposed
0 voters

If you are in favor but have reservations, or are opposed but something could change your mind, please explain in a reply.

We want everyone to be heard, but many posts repeating the same thing actually makes that harder. If you have something new to say, please say it. If, instead, you find someone has already covered what you’d like to express, please simply give that post a :heart: instead of reiterating. You can even do this by email, by replying with the heart emoji or just “+1”. This will make long topics easier to follow.

Please note that this is an advisory “straw poll” meant to gauge sentiment. It isn’t a vote or a scientific survey. See About the Change Proposals category for more about the Change Process and moderation policy.

This change proposal has now been submitted to FESCo with ticket #3550 for voting.

To find out more, please visit our Changes Policy documentation.

Thank you for filing this Change Proposal!

FESCo has approved this change.

Next Steps:

  • Continue implementation and keep the tracking bug updated
  • Update the bug to MODIFIED when the change is testable (Code Complete)
  • Update to ON_QA when 100% complete and ready for testing

Links:

If you have questions, please reach out!