Hey,
On Sonntag, 11. April 2021 20:18:51 CEST Eric Valette wrote:
> > I think it is not a bug of the package. But it is definitely not severity
> > grave as Akonadi is perfectly usable here in exact the same version
> > (usable to the extent Akonadi works reliable, but that is an upstream
> > issue). So downgrading severity to normal.
>
> When only akonadi-backend-sqlite is installed as you can see in
> installed packages I find normal that the default config file is changed
> to use sqlite by default as I would expect that removing
> akonadi-backend-mysql would remove the mysql backend if it was used with
> a warning.
>
> But apparently, you are more interested in having the package without
> bug than working to simplify your user's life.
We see this as a bug, too. Otherwise we would close this bug as invalid ;)
Debian can't easily distinguish, if you only installed one backend or differnt
ones. Well we could add logic to detect this, but that would be very error
prune.
So the proper solution needs to be done upstream aka in Akonadi directly.
Akonadi has no support to check what different backends are available but
simply try to start mysql. And if you tried it once, than Akonadi has created
a user config that selects the mysql database and it is outside our control to
switch the backend. Because Debian packages are not allowed to touch any stuff
in $HOME.
Never the less in future for trixie the situation needs to be improved, as
Akonadi switched its default backend over to SQLite (see #1034561). Detecting
available backends is becoming a bigger issue.
Any help from your side to fix the problem is highly welcome: merge request,
upstream bug report, patch etc. Unfortunately the Debian maintainers team is a
lot of work and not enough resources, to do all work.
Regards,
hefee
#1034561: https://bugs.debian.org/1034561
signature.asc
Description: This is a digitally signed message part.
