Comment # 10 on bug 958548 from Curtis J Blank

And...

Well it gets frustrating. If I don't catch it and let the Online Update update
mariadb then mariadb breaks and since this server is used for data collection
on a minute by minute basis I lose data. That is unacceptable.

I noticed the latest mariadb is 10.0.27 but there is no guarantee that it is
fixed and again if I try it and it isn't I lose data.

Now when you drop support for 13.2 and I have to go to leap and if 10.0.20 is
not available there and this problem isn't fixed then what am I supposed to do?
This problem started in 10.0.21, A YEAR AGO, and as far as I know persists in
every subsequent version. At least all the ones I tried.

I will restrict myself to technical comments if and when you address things in
a timely fashion and stop allowing the version to fall off support so you can
close tickets without fixing the problems.

So tell me, I really want to know, what am I do do when 13.2 is not supported
and you haven't fixed this?