On Mittwoch, 18. Juni 2025 08:16 Otto Kekäläinen wrote: > Thanks for the source code pointer, but there is no "API" documentation > there, so you should give the exact "API call" you want the script to run. > I assume it is something more complex than `(sudo) akonadi stop`.
Well it is that easy ;) # connect to correct dbus session of the user akonadictl stop # as user # perform the upgrade akonadictl start # as user #done to check if the mysql backend for Akonadi is used: check if that stanza is inside $XDG_CONFIG_HOME/akonadi/akonadiserverrc [%General] Driver=QMYSQL The tricky part is to prevent akonadi to be started again, as it is started, if any service wants to get data. I think we should "just" inform while upgrading, that some Akonadi sessions are running and that users should stop those sessions than wait for the user to hit "OK" and than go on with the mariadb upgrade. On Akonadi side we can add the information, that the mariadb server needs to be stopped, when doing a mariadb server upgrade. This would at least improve the current situations. Maybe someone finds a better integration. Btw. postgresql has the same issue, that an Akonadi session needs to be upgrades. But postgresql all us to install version based packages as they can be co-installed on one system. That makes it possible to perform an upgrade later. For Akonadi to do a postgresql upgrade it needs the old and the new version packages to be installed. Still this is a pain, as you need to the information flow between the administrator and the user. Yes co-installable versions for mariaDB would be a solution, but this is a wishlist for upstream and not possible for Debian to do. Regards, hefee
signature.asc
Description: This is a digitally signed message part.
