[MDEV-31923] Mariadb 10.4 + 10.6 for Bookworm Created: 2023-08-15  Updated: 2023-12-05  Resolved: 2023-08-18

Status: Closed
Project: MariaDB Server
Component/s: Repositories
Affects Version/s: 10.4, 10.6
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Alexander Lausten Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: Compatibility
Environment:

Debian Bookworm



 Description   

Hello, I saw that you just released Mariadb 10.11 + 11.0 for Debian Bookworm, thanks for the great work.

We host both Magento 2 and Shopware 6, is there any planned release for Mariadb 10.4 + 10.6?

Magento 2, has a hard requirement on those versions, so we would love to know whats ahead so we can act accordingly.



 Comments   
Comment by Daniel Black [ 2023-08-15 ]

The trouble with releasing < 10.11 on Bookworm is that 10.11 is already packaged by Debian bookworm so can cause conflicts.

You can use podman to run a Docker Official Image of MariaDB (any version) and install that as a systemd service.

How hard are the requirements? MariaDB releases always aim to be backwards compatible. version can be set in the configuration files to fake a version for an application that checks (just like this JIRA instance).

Comment by Alexander Lausten [ 2023-08-15 ]

Thanks for your fast reply Daniel, I have tested the suggested version variable with some docker containers for our local build and at first sight it seems to be working flawlessly.

I will be testing it on some staging Bookworm staging servers in September and update the task.

Comment by Daniel Black [ 2023-08-18 ]

Sorry to advise you of a Shopware error with latest MariaDB that you should know about- https://github.com/shopware/platform/issues/3273

closing this as resolved for now, but feedback welcome when you get to it.

Comment by Pedro Veiga [ 2023-12-05 ]

I also found that specifying "--os-type=debian --os-version=bullseye" when running the install script also works. Is there any known problem by doing like that?

Generated at Thu Feb 08 10:27:29 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.