It's me again!
Otto,
I found out that it is an Akonadi problem: Akonadi uses Mariadb as default
database, but does not provide mysqlcheck through dependencies.
Now I could repair the table structure with that knowledge, see the attached
file.
Would you please add the Akonadi maintainer to this
Otto,
I don't have the crashed database available. What I say is, that I have 3
working Akonadi databases, one in a fresh Bullseye install.
In any case the call of mysql_upgrade fails.
bequimao@bullseye-kde-vm:~$ mysql_upgrade --defaults-file=/home/
bequimao/.local/share/akonadi/mysql.conf --soc
Otto,
Let us concentrate on the migration program mysql_upgrade, as quoted in the
title.
I attach the output of the test in Fedora. So you see what I do expect. It is
the program to check and repair the database schema. It is a regression in
Debian, not an upstream issue.[bequimao@fedora34 ~]$
The user in the forum has already recovered his mails and data, so he won't
risk the test.
My point is, that in 2 of my 3 debian installations there are errors in the
MariaDB system tables (see mysql.err). Only the fresh Bullseye installation is
without errors. Akonadi/Contact/KMail works in a
Package: mariadb-server-core-10.5
Version: 1:10.5.11-1
Severity: normal
File: mariadb-server-core
Dear Maintainer,
The redo log was corrupted before upgrade to Debian bullseye. Akonadi would
not start.
see
https://debianforum.de/forum/viewtopic.php?f=29&t=181760&start=15#p1280104
(German
5 matches
Mail list logo
