[debian-mysql] Bug#1032047: mariadb-server: Preinst fails if user has mariadb running while system service stopped.

[Otto Kekäläinen]

This is still waiting for input from Akonadi maintainers:

On Thu, 2 Mar 2023 at 23:44, Otto Kekäläinen <otto at debian.org> wrote:
>
> (Adding akonadi-backend-mysql maintainers as recipients)
>
> Hi!
>
> When MariaDB Server upgrades, it could trigger a restart in
> akonadi-backend-mysql, or the maintainer scripts could directly stop
> the akonadi-backend-mysql. I am open to any solution here.
>
> The main question is: what are the expectations from Akonadi on
> MariaDB upgrades?
>
> If MariaDB completely ignores Akonadi, you might run into problems
> because Akonadi/mysqld did not have a clean shutdown on MariaDB 10.5
> and then MariaDB 10.11 will fail to start because crash recovery
> across major versions. Before going into major version upgrade the old
> server needs to be stopped gracefully with for example `pkill mysqld`
> (or a more elaborate version matching other binary names and checking
> for process owning user etc). If MariaDB stops the server something
> needs to exist to restart it.
>
> Merge Requests on Salsa against
> https://salsa.debian.org/mariadb-team/mariadb-server/-/blob/debian/latest/debian/mariadb-server.preinst#L27-47
> are welcome!


And side note: the libmariadb3 issue was reported in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031773,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031863 and
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031860 and
forwarded upstream in
https://lists.launchpad.net/maria-discuss/msg06508.html