Bug#915130: [debian-mysql] Bug#915130: Further information

2018-12-21 Thread Faustin Lammler
Yannik Sembritzki ,
21/12/2018 - 23:00:33 (+0100):

> thanks for linking the upstream bugreport!
> Seeing that it is from 2015, it would be great to get some traction on
> this and finally have this fixed in the debian repo as well :-)
Of course and I think this should not be so difficult. But currently
most of the forces are working on including 10.3 in the next stable
Debian release so I don't know when this issue will be resolved.

> By the way, did you check whether this is fixed in 10.3 only or also in
> the 10.1 package from the mariadb.org repositories.
As said, I have tested 10.1 and 10.3 from mariadb repo, they are both
OK.

If you have time and want to contribute on a patch, feel free to read
this :-)
https://wiki.debian.org/Teams/MySQL/patches

Have a nice week-end,
-- 
Faustin Lammler



Bug#915130: [debian-mysql] Bug#915130: Further information

2018-12-21 Thread Yannik Sembritzki
Hi Faustin,

thanks for linking the upstream bugreport!
Seeing that it is from 2015, it would be great to get some traction on
this and finally have this fixed in the debian repo as well :-)

By the way, did you check whether this is fixed in 10.3 only or also in
the 10.1 package from the mariadb.org repositories.

Best regards
Yannik



Bug#915130: [debian-mysql] Bug#915130: Further information

2018-12-21 Thread Faustin Lammler
Hi Yannik,
thanks for your report!

I am able to reproduce this and the problem is only present in the
Debian package version of MariaDB.

This bug seems also described there:
https://jira.mariadb.org/browse/MDEV-8457

If this is an acceptable solution until the bug is resolved, you can use
the 10.1 (on 10.3 it is working too) version from official MariaDB
repository.
https://downloads.mariadb.org/mariadb/repositories/

Regards,
Faustin