Hi Guillaume!
Now I understand your concern. Please, next time, go strait to the point
it will avoid so many emails trying to understand what the concern was
in the first place. There is often some confusion between MariaDB repos
and Debian official repos, that's why I did not understand it
immediately.

Guillaume Lefranc via discuss <[email protected]>,
03/04/2026 – 22:13:21 (+0700):

> I am very aware of how Debian works, let's cut to the chase.
> Your point is somewhat moot. Trixie also packages gcc-12 and gcc-13, so if
> the issue is compiler friction, an older version of GCC can always be used.
> I haven't tried to backport 10.11 myself for Trixie but I'm quite sure it's
> possible without any major refactoring.

MariaDB is an opensource project, if you are willing to help building
MariaDB 10.11 or 11.4 for Trixie, you are more than welcome!

> My question is more about why the MariaDB Foundation isn't willing to build
> these for us.

MariaDB is a non profit Foundation with limited ressources. Building and
testing 2 more version for Debian 13 on 4 architectures represents a lot
of work. And, Otto (which seems to be quite skilled at maintaining
successfully this big package for a couple of years in Debian and Ubuntu),
does not think that it's that straightforward... Maybe that's one of the
reason.

Also, it's probably not that "MariaDB Foundation isn't willing to build"
it for the community, but more: this is how it has worked until now, we
do not backport release on Debian and start from the release that is
packages in Debian officially (maybe I am wrong on that point).

With all that said, your concern seems perfectly valid. And, you are
definitively right, people should not be forced to upgrade to too recent
MariaDB versions.

If maybe it's an easy task, then again, I really encourage you to
contribute.

--
Faustin Lammler
MariaDB Foundation
GPG: F652 BCD1 1AA8 8975 F010 48A5 390A 2F27 832A 5C79

Attachment: signature.asc
Description: PGP signature

_______________________________________________
discuss mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to