[debian-mysql] MariaDB in Jessie

[Otto Kekäläinen]

Hello!

Thanks Jonathan for taking the time to review the MariaDB packaging
and thanks for your bug reports.

2014-09-14 1:01 GMT+03:00 Jonathan Wiltshire <jmw at debian.org>:
> On 2014-08-26 11:27, Colin Charles wrote:
>>
>> Upstream will publish security releases for many years to come -- it
>> is the choice of Red Hat Enterprise Linux 7, so the commitment is
>> there
>
>
> Can you quantify this? I mean, did anyone actually ask upstream what their
> support commitment is going to be?

Yes, as Clint said, Colin told us this and he is the community manager
at MariaDB. It is however always better to have a official written
statement at mariadb.org, and I did find this page that says 5.5 is
supported until 2017:
https://mariadb.com/kb/en/mariadb/development/mariadb-maintenance-policy/

Colins statement however points out that 5.5 will really be supported
even longer due to it being a very widely used release. To be sure we
don't loose such important information I've included this link and
security upgrades documentation in the maintainer documentation:
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/tree/debian/README.Maintainer
This is not required by policy but I think it is important that e.g.
the security team can easily do upgrades to the package even if the
primary maintainer for some reason would not be quickly available..


>>> However, newer is always newer, so shipping MariaDB 10.0 would be nice
>>> if we have time to finalize it after it comes out from the NEW queue..
>>>
>>
>> I agree.
>
>
> 10.0 left NEW on 26th August. Since then, it hasn't been uploaded to
> unstable, though I do see a version on mentors from yesterday.

It was uploaded to experimental. See details at
https://tracker.debian.org/pkg/mariadb-10.0
On 27th to 31st I upgraded the package from 10.0.10 to 10.0.13 and
"frontported" all packaging improvements done to 5.5 while 10.0 sat in
the NEW queue but at the since that nothing has happened because I
don't have an active sponsor for 10.0.


> It has the following problems:
>
>  - lintian error build-depends-on-obsolete-package

The deprecated usage of hardening-wrapper is common across all
mysql-5.5, mysql-5.6, mariadb-5.5 and mariadb-10.0. I've tried to
raise discussion about what the optimal solution is, because it is
certainly not a trivial thing and we don't want to end up in a
situation where the any binary would "accidentally" not be hardened.
I'll post a separate message about this on this list today.

>  - rewrites changelog history

It seems there was a changelog change when it was uploaded into
experimental which never found it's way into the git repo. I've now
fixed this, see my commits today at
http://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.0.git/log/


> It's past the end of transitions for Jessie. Does moving from MariaDB 5.5 to
> 10.0 in Jessie have any transition implications? There's at least one symbol
> that goes away completely.

The libmysqlclient18 -> libmariadbclient18 soname change was done on
request be senior Debian Developers with the main motivation that two
libraries from different packages should not provide the same shared
library in Debian. Upstream however continues to use the exactly same
library name as MySQL because they want to be a drop-in-replacement. I
don't think anybody has done any binaries that uses this special
libmariadbclient18 so we can do whatever we want to it at this stage.

Actually I've even thought about the option to drop libmariadbclient18
completely and promote the usage of mariadb-client-lgpl package that
recently landed in Debian testing. I haven't though had the courage to
do this decision yet - I'd like to hear opinion of others first.
Details about this at https://wiki.debian.org/Teams/MySQL/MariaDBPlan


Jonathan, can you please subscribe to this list and continue to share
feedback here? Thanks!

- Otto