Processed: Fwd: Re: Sqlite akonadi transaction mode fix

2015-01-31 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: tag 775990 -moreinfo Bug #775990 [akonadi-backend-sqlite] [akonadi-backend-sqlite] Akonadi reports deadlocks Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 775990:

Bug#775990: Fwd: Re: Sqlite akonadi transaction mode fix

2015-01-31 Thread Sandro Knauß
bug? This one should go upsteam. Can you check for a matching bug (bugs.kde.org) - if there is none create a new one. Afterwards please let us know the bugnr. regads, sandro -- Weitergeleitete Nachricht -- Betreff: Re: Sqlite akonadi transaction mode fix Datum: Montag, 26

Re: Sqlite akonadi transaction mode fix

2015-01-26 Thread David Goodenough
On Wednesday 21 January 2015 09:49:18 David Goodenough wrote: I use KdePIM and thus akonadi with SqLite. I am running unstable and am up to date with fixes. Looking in the KDE bug database I found:- http://osdir.com/ml/kde-commits/2014-07/msg02228.html which seems to address the

Re: Sqlite akonadi transaction mode fix

2015-01-22 Thread Sandro Knauß
Hey, The only errors I am getting are the deadlocks, and this patch at least purports to fix them. Hence my interest in using it. The patch looks logical and simple. ah okay there is a patch to solve this issue - NICE. So we should think about getting that patch to debian. It would be nice

Re: Sqlite akonadi transaction mode fix

2015-01-22 Thread Martin Steigerwald
Am Donnerstag, 22. Januar 2015, 12:58:13 schrieb Sandro Knauß: Hey, The only errors I am getting are the deadlocks, and this patch at least purports to fix them. Hence my interest in using it. The patch looks logical and simple. ah okay there is a patch to solve this issue - NICE.

Re: Sqlite akonadi transaction mode fix

2015-01-22 Thread David Goodenough
On Thursday 22 January 2015 12:11:09 Martin Steigerwald wrote: Am Donnerstag, 22. Januar 2015, 12:05:40 schrieb Martin Steigerwald: Am Donnerstag, 22. Januar 2015, 10:39:38 schrieb David Goodenough: On Thursday 22 January 2015 10:50:53 Martin Steigerwald wrote: Am Mittwoch, 21. Januar

Re: Sqlite akonadi transaction mode fix

2015-01-22 Thread Martin Steigerwald
Am Donnerstag, 22. Januar 2015, 13:57:11 schrieb Sandro Knauß: Hey, So we should think about getting that patch to debian. It would be nice if you create a debian bugreport against akonadi-backend-sqlite. this one can interpet as serious/grave bug against this package, cause it makes

Re: Sqlite akonadi transaction mode fix

2015-01-22 Thread Sandro Knauß
Hey, As for building yes, so the setting is just about what is being used as default when no config exists yet? Jepp, and to be honest I never touched that parameter and got all backends. Regads, sandro -- The only option that should be set in the cmake step is where to install

Re: Sqlite akonadi transaction mode fix

2015-01-22 Thread Martin Steigerwald
Am Donnerstag, 22. Januar 2015, 10:39:38 schrieb David Goodenough: On Thursday 22 January 2015 10:50:53 Martin Steigerwald wrote: Am Mittwoch, 21. Januar 2015, 09:49:18 schrieb David Goodenough: I use KdePIM and thus akonadi with SqLite. I am running unstable and am up to date with

Re: Sqlite akonadi transaction mode fix

2015-01-22 Thread David Goodenough
On Thursday 22 January 2015 12:21:29 Sandro Knauß wrote: Hey, as martin already mentiond: SQLite is really not the preferend database backend. I played around with it for some time and it triggers randomly Database Errors. The base problem, is that sqlite only allows one writing thread,

Re: Sqlite akonadi transaction mode fix

2015-01-22 Thread Diederik de Haas
On Thursday 22 January 2015 11:30:54 Martin Steigerwald wrote: I have akonadi-server version 1.13.0-2 but I guess that's not the version you're talking about? Because MySQL still uses quite some CPU time on my machine ... I don´t think 1.13 git branch changes I am talking about are in the

Re: Sqlite akonadi transaction mode fix

2015-01-22 Thread Sandro Knauß
Hey, as martin already mentiond: SQLite is really not the preferend database backend. I played around with it for some time and it triggers randomly Database Errors. The base problem, is that sqlite only allows one writing thread, that's why you get deadlocks with sqlite. I'm glad if I can

Re: Sqlite akonadi transaction mode fix

2015-01-22 Thread Martin Steigerwald
Am Donnerstag, 22. Januar 2015, 12:05:40 schrieb Martin Steigerwald: Am Donnerstag, 22. Januar 2015, 10:39:38 schrieb David Goodenough: On Thursday 22 January 2015 10:50:53 Martin Steigerwald wrote: Am Mittwoch, 21. Januar 2015, 09:49:18 schrieb David Goodenough: I use KdePIM and thus

Re: Sqlite akonadi transaction mode fix

2015-01-22 Thread Sandro Knauß
Hey, DATABASE_BACKEND MYSQL IMO you do not set the Database on your own. if libsqlite is available the backend is build. The only difference if, the missing of sqlite or mysql is ending up in a error or only a warning about the missing dependency. The only option that should

Re: Sqlite akonadi transaction mode fix

2015-01-22 Thread Martin Steigerwald
Am Donnerstag, 22. Januar 2015, 12:37:18 schrieb Sandro Knauß: Hey, DATABASE_BACKEND MYSQL IMO you do not set the Database on your own. if libsqlite is available the backend is build. The only difference if, the missing of sqlite or mysql is ending up in a error or only a

Re: Sqlite akonadi transaction mode fix

2015-01-22 Thread Sandro Knauß
Hey, So we should think about getting that patch to debian. It would be nice if you create a debian bugreport against akonadi-backend-sqlite. this one can interpet as serious/grave bug against this package, cause it makes the package more or less not working, so this one can make its way into

Re: Sqlite akonadi transaction mode fix

2015-01-22 Thread Diederik de Haas
On Thursday 22 January 2015 10:50:53 Martin Steigerwald wrote: As for updates to Debian packages, I´d like to see current akonadi 1.13 branch packages, cause it contains quite some noticeable performance updates regarding database access that made MySQL disappear from cpu usage top for most

Re: Sqlite akonadi transaction mode fix

2015-01-22 Thread Martin Steigerwald
Am Donnerstag, 22. Januar 2015, 11:09:46 schrieb Diederik de Haas: On Thursday 22 January 2015 10:50:53 Martin Steigerwald wrote: As for updates to Debian packages, I´d like to see current akonadi 1.13 branch packages, cause it contains quite some noticeable performance updates regarding

Re: Sqlite akonadi transaction mode fix

2015-01-22 Thread Martin Steigerwald
Am Mittwoch, 21. Januar 2015, 09:49:18 schrieb David Goodenough: I use KdePIM and thus akonadi with SqLite. I am running unstable and am up to date with fixes. No. Its no default. Default is Akonadi with MySQL. If you use SQLite, AFAIK you chose that yourself explicetely. So its no thus here,

Re: Sqlite akonadi transaction mode fix

2015-01-22 Thread David Goodenough
On Thursday 22 January 2015 10:50:53 Martin Steigerwald wrote: Am Mittwoch, 21. Januar 2015, 09:49:18 schrieb David Goodenough: I use KdePIM and thus akonadi with SqLite. I am running unstable and am up to date with fixes. No. Its no default. Default is Akonadi with MySQL. If you use

Sqlite akonadi transaction mode fix

2015-01-21 Thread David Goodenough
I use KdePIM and thus akonadi with SqLite. I am running unstable and am up to date with fixes. Looking in the KDE bug database I found:- http://osdir.com/ml/kde-commits/2014-07/msg02228.html which seems to address the repeated dialog boxes I get while filters run on my mailboxes, and the log