Comment # 10 on bug 1178799 from Danilo Spinella

(In reply to Christopher Yeleighton from comment #9)
> (In reply to Danilo Spinella from comment #8)
> > Is this the default configuration of akonadi? Or is it your custom
> > configuration? I'd instead use a single system instance of mariadb, handled
> > by systemd. In this case, the mariadb package stops the server before
> > updating it and then restart it, so there shouldn't be any breakage.
> 
> It is the default configuration promoted by KDE PIM.  The update should just
> examine whether a mariadb server is running for whatever reason and refuse
> to be applied.  There is no need to rely on systemd to answer that question.

I have checked the spec file, and it doesn't seem that mariadb is stopped
before updating. So it continues running fine. This is the update message:

WARNING: You are upgrading from different stable version of MySQL!

Your database will be migrated automatically during next restart of MySQL.
Before you do that make sure you have up to date backup of your data. It
should be mainly in $datadir directory.

If it works like this I can't force users to stop the instances before
updating. 

(In reply to Christopher Yeleighton from comment #6)
> The akonadi server keeps running while the mariadb package is being updated. 
> AIUI, it can cause some serious breakage in the mariadb journal, potentially
> leading to a data loss.

We also might want to revisit this, this error might be due to something else,
I am not sure. Maybe we can get akonadi upstream opinion on this.