MariaDB 11.4.x installation fails on AlmaLinux 10

Support
1

Hello

I tried to install MariaDB 11.4 on AlmaLinux 10. I used the repo as i used on AlmaLinux 9:

[mariadb]
name=MariaDB 11
baseurl=https://yum.mariadb.org/11.4/rhel9-amd64
gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
gpgcheck=1
module_hotfixes=1

I run the installation with this: dnf install MariaDB-client MariaDB-server MariaDB-shared and i failed:

Problem: package MariaDB-server-11.4.7-1.el9.x86_64 from mariadb requires galera-4, but none of the providers can be installed
  - cannot install the best candidate for the job
  - nothing provides libboost_program_options.so.1.75.0()(64bit) needed by galera-4-26.4.16-1.el9.x86_64 from mariadb
  - nothing provides libboost_program_options.so.1.75.0()(64bit) needed by galera-4-26.4.18-1.el9.x86_64 from mariadb
  - nothing provides libboost_program_options.so.1.75.0()(64bit) needed by galera-4-26.4.19-1.el9.x86_64 from mariadb
  - nothing provides libboost_program_options.so.1.75.0()(64bit) needed by galera-4-26.4.20-1.el9.x86_64 from mariadb
  - nothing provides libboost_program_options.so.1.75.0()(64bit) needed by galera-4-26.4.21-1.el9.x86_64 from mariadb
  - nothing provides libboost_program_options.so.1.75.0()(64bit) needed by galera-4-26.4.22-1.el9.x86_64 from mariadb

So i run dnf install boost-program-options to install the required software. It didn’t not help. Probably the version 1.83.0-5 is to new for MariaDB.

What else can i do? Or should i simply wait until everything is officially ready for AlmaLinux 10?

Thanks!

Kind regards

Martrin

2

If you specifically need MariaDB 11.4 on AlmaLinux 10, then yes. You’ll need to wait until upstream adds support for RHEL 10.
They don’t provide RHEL 10 packages yet:

Or, you can install MariaDB 10.11 from the AppStream repo if that works for you.

3

Executables (binaries) are typically built as in compiled and linked. The linking combines object files into executable with calls to external libraries – shared objects.
When program is run, dynamic linker connects the binary to the shared objects that the system has. The system where you run the program may not be the same as the system where the program was built; the libraries have to be binary compatible for the run to succeed.

The error is not directly from that though. When the RPM package was built, it got also metadata about (some) libraries (e.g. libboost_program_options.so) that it requires. This way package manager can already tell what is needed. (The error messages from dynamic linker can be more cryptic.)

There is a “plan B”:

  • Get the src.rpm source package from which the MariaDB-server-11.4.7-1.el9.x86_64 package has been built from
  • Build (with mock) the binary packages for el10
  • Install the packages

This can be a rabbit hole as the build may require other packages that el10 does not have. Furthermore, the requirement for specific version of libboost_program_options could be stated in the spec – the build instructions within the source package – and then the build cannot use the available Boost version (1.83.0-5) automagically.

4

Actually the application needs MariaDB 11.4, but i am not in hurry and i can wait.

Thanks!