Hej Otto,
Am Mittwoch, 18. Juni 2025, 08:16:33 CEST schrieb Otto Kekäläinen:
> 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`.
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`.
Hej Otto,,
Am Montag, 16. Juni 2025, 19:55:23 CEST schrieb Otto Kekäläinen:
> > but `akonadictl stop` for each user after connecting to their dbus
> > session should do it from a technical point of view.
> > Maybe first diverting some files to prevent the user from starting
> > them up again, and
> but `akonadictl stop` for each user after connecting to their dbus session
> should do it from a technical point of view.
> Maybe first diverting some files to prevent the user from starting them up
> again, and then diverting back once upgraded.
>
>
> But all of this is a bit euww.
If you ship
On Monday, June 16, 2025 1:17:13 PM CEST Otto Kekäläinen wrote:
> In Debian packaging we can't do anything about upstream capability to
> recover from crashes. Please suggest what exact Akonadi service
> starts/stops the database and how we can ask Akonadi to shutdown before
> server upgrade. At le
In Debian packaging we can't do anything about upstream capability to
recover from crashes. Please suggest what exact Akonadi service
starts/stops the database and how we can ask Akonadi to shutdown before
server upgrade. At least it would cover the common case if regular upgrades.
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,
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).
A variant of it was
https://bugs.debian.org/c
Hi,
We're running out of time for trixie.
On 23-03-2025 11:01, Paul Gevers wrote:
On Thu, 27 Apr 2023 10:32:09 +0200 Sune Stolborg Vuorela
wrote:
To me it looks like 1032047 has been fixed with a solution that makes
this more likely to happen rather than list.
As far as I understand the pr
Control: retitle -1 akonadi server not robust against mysql upgrades
On Thu, 27 Apr 2023 10:32:09 +0200 Sune Stolborg Vuorela
wrote:
To me it looks like 1032047 has been fixed with a solution that makes this more
likely to happen rather than list.
As far as I understand the problem (as expr
Control: tags -1 +moreinfo
Control: severity -1 serious
On Thursday, April 27, 2023 8:05:50 AM CEST Didier 'OdyX' Raboud wrote:
> Le vendredi, 10 mars 2023, 21.04:56 h CEST Patrick Franz a écrit :
> > the issue is connected to MariaDB when upgrading after the shutdown was
> > not clean, see https:
Control: tags -1 +moreinfo
Control: severity -1 important
Le vendredi, 10 mars 2023, 21.04:56 h CEST Patrick Franz a écrit :
> the issue is connected to MariaDB when upgrading after the shutdown was
> not clean, see https://bugs.debian.org/cgi-bin/bugreport.cgi?
> bug=1032047#40
>
> We are trying
Hi,
the issue is connected to MariaDB when upgrading after the shutdown was
not clean, see https://bugs.debian.org/cgi-bin/bugreport.cgi?
bug=1032047#40
We are trying to find a solution for this.
--
Med vänliga hälsningar
Patrick Franz
Package: akonadi-backend-mysql
Version: 4:22.12.2-1
Severity: grave
X-Debbugs-Cc: cqu...@arcor.de
I cannot use my kmail email client due to akonadi server not being started. To
debug it I have tried the following:
# akonadictl start
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.ak
14 matches
Mail list logo
