On Sunday, June 15, 2025 12:13:48 PM CEST Otto Kekäläinen wrote: > H!, > > I just found this issue > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032240) when > browsing the list of release critical issues for Trixie (although it > is from 2023 and was open also when Bookworm was released, so not > really a Trixie issue).
> Akonadi maintainers - please suggest how you want to solve this. My suggestion is for mariaDB to not be so rigid in only being able to recover exact versions. I could see the same thing actually happen "unclean server crash, server administrator reboots into some emergency shell, while at it does a system upgrade that brings in a newer mariaDB". I'm not sure how a user process should be able to actually deal with this. Not running an upgrade while being in a graphical user session would probably prevent 95% of the akonadi issues. But it still misses the one case I previously described (that occurred to me) - My workstation locked up for unknown reason - I power cycled the work station - Before logging in, I switched to a terminal to do some system maintenance - A newer mariaDB would not fix the previous unclean stop of an older version I'm not sure how this can be dealt with in any other ways than in mariaDB itself. I'm unsure though if upstream's work towards making sqlite the new default backend and various migration helpers is in the version we are releasing with in trixie or not. /Sune -- I didn’t stop pretending when I became an adult, it’s just that when I was a kid I was pretending that I fit into the rules and structures of this world. And now that I’m an adult, I pretend that those rules and structures exist. - zefrank
