> Some poking around on Github suggests that the fix is > https://github.com/MariaDB/server/commit/47f8a18fec604983e47fdf7c822d94b26d85cade > > If this is actively breaking systems, couldn't we simply apply that > patch to the current versions in stretch and buster, as a least-change > option?
We could in theory extend the gitlab-ci.yml pipeline to include a test that sets up a replication master and a slave, and runs some updates and replicates them. With that pipeline we could validate that earlier versions worked and with this patch it works again. And such an addition to the CI pipeline would also discover if replication ever breaks again. This is however too much work for me right now, so instead I would just wait until upstream releases and trust that upstream knows what they are doing in terms of making the fix correctly without breaking anything more somewhere else.
