Details
-
Type:
Task
-
Status: Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Fix Version/s: 5.5.33a-galera
-
Component/s: None
-
Labels:
Description
MariaDB 5.5.33 release introduced incompatibility between deb packages of client library versions >= 5.5.33 and server versions <= 5.5.32.
The incompatibility itself was expected and should not have been a problem since the client and server are supposed to be upgraded together, but what we didn't take into account was that we use the same repository for MariaDB Galera, even if it has a different version number. So, currently we have the official repository with 5.5.33a server, client and client library, and with 5.5.32 Galera server. It does not allow the server to be installed because it requires the client library but cannot install it due to incompatibility.
Thus, we need to release 5.5.33 Galera server a.s.a.p, to catch up with the client libraries.
The alternative solution is to create a separate repository for Galera (and to change the repository tool accordingly), but it will mean storing a lot of duplicate packages.
Yet another alternative solution is to create a symlink to the Galera repo (and change the repository tool accordingly), so that it normally points at the official repo, but sometimes, like now, at an older repo; but it will mean either using the same older repo regardless the mirror, or taking into account how mirrors store older versions, which might be not very simple.
Gliffy Diagrams
Attachments
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
We have a new revision of MariaDB Galera Cluster being built/tested in Buildbot currently. Once everything goes well there the next step is some additional installation/upgrade testing and then if everything looks alright it's time for a release. So not far away anymore.
MaraDB-Galera 5.5.33a has been released
could we get a status update on this?