hello - i am trying to install mariadb 11.8.2 (latest stable) on RL-10. just using ordinary dnf install gives me V 10:11
but when i do:
./mariadb_repo_setup --mariadb-server-version=“11.8.2” ;
i get the following message:
# [error] Detected RHEL or compatible but version (10.0) is not supported.
is there a way to get 11.8 installed on 10? is it too early to even try?
(sorry if this is the wrong forum)
EDIT: i looked here: Index of /yum/11.8.2/ but I dont see RL-10 listed.
The baseline is that Rocky has what RHEL has. Those are described in Red Hat Enterprise Linux Application Streams Life Cycle | Red Hat Customer Portal
That is, RHEL 10 has MariaDB “10.11” as Full Life Application Stream. That is, supported to 2035.
Likewise, RHEL 9 has MariaDB “10.5” supported to 2032.
In addition, RHEL 9 has MariaDB “10.11” Application Stream, supported to 2028.
It is possible that RHEL 9 will get a new MariaDB Application Stream to replace the “10.11”, but the “10.5” will remain available the whole RHEL 9 lifetime.
Similarly, RHEL 10 may get a newer version of MariaDB as Application Stream later.
What is provided in RHEL is supported by Red Hat, with backported (security) fixes.
The idea of Enterprise Linux is that you can set up a MariaDB (nominally 10.11) server now and use it until 2035.
The “ordinary dnf install” is the intended way to manage software in Rocky.
Use of some script smells like “source install”, which one should not do as it can mess up the package management. (Exception: source install as regular user to outside of system directories should be safe.)
The alternative is to not use what RHEL/Rocky has. To use third-party packages/applications.
Those are not supported by Red Hat nor Rocky. The builds and support must come from those
third parties.
The mariadb.org is a “third party” in this context. If you want them to build packages for rhel10/rocky10, then you must contact them about it.
Yes, the el10 is still very new.
For now you would have to use CentOS Stream repository to get MariaDB 11.8.2. From the dropdown box, you can see for Red Hat they don’t have EL10 yet, only EL8 and EL9.
Ideally, better to wait until they build a repository for EL10. There is no real need to run the latest and greatest MariaDB.
That seems to have subdirs for releasevers 7, 8, and 9. No “10”.
True, technically we could even argue that CentOS 7 is not Stream, since Stream didn’t appear until at least CentOS 8. CentOS Stream is about the closest they would get to EL10 at the moment anyway. If you also visit the link I put in my post, it says “CentOS Stream” in the dropdown. It doesn’t state whether it’s 7, 8, 9 or 10. That said, referencing $releasever in the yum repo file will most likely fail for CentOS 10 Stream anyhow if they haven’t provided for it. MariaDB should therefore at least state which Stream versions are supported in their dropdown list at least.
But either way, as I mentioned, there’s no need to run the latest and greatest MariaDB anyhow, and better to wait until they release for EL10.
I’ll just add this here too: MariaDB | endoflife.date
Since EL9 and EL10 come with MariaDB 10.11, there is a supported version for another 2 years at least - even if we don’t include the fact that Red Hat backport fixes to their version of packages. Even including that, we have MariaDB in RHEL9 supported until 2032, and 2035 for EL10.
If people are wanting the latest and greatest packages immediately, then you’re using the wrong Linux distribution. I expect MariaDB 11.x will perhaps appear in EL10 at some point, but I can’t see it happening for at least six months if not more. And if not, it will be resolved anyway when MariaDB start building packages for EL10, and you can then use the third-party MariaDB repository.
but you forget there is something sexy about having the latest version of MariaDB since it contains features we probably don’t use or need (yet).
This sounds like excellent advice.
indeed, previously i have manually created/copied a repo and put it into /etc/yum.repos.d/MariaDB.repo but now i appreciate and understand its best to avoid doing that. i probably started doing that when there was a required new feature of MySQL (its almost painful to type that name out).
EDIT: i would like to thank the RL community. you are a great group of folks to communicate with.
That is a special case. The /etc has mostly configuration files and typically ok and even expected that you override system defaults by adding files (manually) to the /etc/servicename.d/ directories (although the /etc/yum.repos.d/ has many *.repo files from packages). Good, unique filenames are huge a topic though.
There are configuration management systems (Rocky includes Ansible) that help in the “manually” part, making it more systematic and reproducible.
The scary source install writes to /usr/bin and /usr/lib64 and does not warn if it overwrites files that are from packages (which corrupts the application from the package). Later, a dnf up that updates that package replaces the files, corrupting the source installed application.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.