Re: KDEPIM issues (was: Re: Bugs bugs bugs)
Hey, > Well, that may not change *that much* with a newer version. 4.14.5 has > some bugs fixed, but I compiled kdepim-runtime and kdepimlibs 4.14.5 on top > of KDEPIM 4.14.2 as packages by debian and I still have most of the > issues. I also run akonadiserver 1.13 branch from git with the MySQL > optimizations, and while that helps with MySQL load, I still have KMail > and Akonadi seem to disconnect with each other at times. It is quite hard to track issues down, if they happen once in a while. I think all kdepim devs so am I try to fix these stuff, but hunting anything non reproducable is a lot of work. > And the Plasma 5 / Qt 5 port of KDEPIM is not yet ready as far as I am > aware of. Even that will use the Akonadi as we now it today, so it may > have still similar shortcomings and bugs. > There is Akonadi Next in prototyping by Aaron Seigo and Christian > Mollekopf, but this is far from finished so far. The porting work for qt5 is done in master - but we won't release it until the new api for akonadi next is outlined. We do not want to stick another release cycle with the current api for akonadi. The current plan is to release in a year. Until than only bugfixes are released for the qt4 version. > I am not sure whether all the fixes for the KDEPIM deployment in Munich > have gone upstream. I had hoped that these would fix quite some of the > longer term issues of Akonadi, but whatever trickled upstream so far did > not seem to fix it. Neither the bugfixes nor enhancment havn't got upstream - they are only available at github and on our obs: https://github.com/kolab-groupware/kdepim https://obs.kolabsys.com/project/show/Kontact:4.13:Development Well hopefully the next weeks give us time to push things upstream. > What could work quite well, and thats why I think for Munich it could > work, would be to have some decent (!) IMAP server like Dovecot (not > Exchange!) together with KMail. kolab uses cycrus as imap server. But dovecot ( I use this personaly) also plays very nicely with kmail. > KDEPIM / Akonadi I think still needs robustness work. But someone has to > do it. And unless I actually contribute to that, I know I need to wait > until someone does. Well akonadi was the first try of such a middelware and we learned a lot of things. And we now know, that was bad/good design descisions, these we went into akonadi next. > In case you want to go that route, I suggest you also subscribe to kdepim- > users and probably kde-pim upstream mailinglists via lists.kde.org and be > prepared to deal with any issues you see, report bugs, help with bug > triaging and try to be patient. > > Thats the situation as I see it today after having myself investing quite > some time into bug reporting, reading up bugs, trying to fix things for me > without going into developing. Doing that might be the next step, but from > the performance fix for Maildir´s KDEPIM devels guided me to some time ago > I got the impression that the Akonadi code base wants some time to > understand it enough to fix any of the longer term, in my eyes, probably > fundamental, issues with it. cewl - I'm looking forward to see more of your work in kdepim; if there is anything where I can assist you - feel free to contact me. regards, sandro -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1457674.DbvhxYp7N6@tabin.local
Re: KDEPIM issues (was: Re: Bugs bugs bugs)
On Sunday 22 February 2015 16:13:10 Martin Steigerwald wrote: > What could work quite well, and thats why I think for Munich it could > work, would be to have some decent (!) IMAP server like Dovecot (not > Exchange!) together with KMail. I have this setup here and indeed dovecot-imap, akonadi and kmail work nicely together for me. All are Debian jessie boxes. Rainer -- Rainer Dorsch http://bokomoko.de/ -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1799689.gj3HT5iYvv@blackbox
Re: KDEPIM issues (was: Re: Bugs bugs bugs)
Am Sonntag, 22. Februar 2015, 16:13:10 schrieb Martin Steigerwald: > Am Samstag, 21. Februar 2015, 16:32:33 schrieb Volker Wysk: > > I've never used the experimental branch. When will the packages migrate > > to Unstable? > > They won´t before Jessie release. > > Maybe KDEPIM 4.14.5 could make it to unstable as its only bug fixes, but > that would need an exception from the release team as well in this late > state of Jessie freeze, I think – unless they fix RC bugs (and only! them). > The freezing / release policy is clarified in some document I don´t have > the URL at hand at the moment, should be easy to find. This should be it: https://release.debian.org/jessie/freeze_policy.html It doesn't predict when Jessie will be released, but I get the impression that it won't be much longer. > > > For me beside KDEPIM KDE / Plasma 4.14.2 really works quite good. > > > KDEPIM basically works, but there are still a lot of open issues. > > > > Exactly... > > Well, that may not change *that much* with a newer version. 4.14.5 has > some bugs fixed, but I compiled kdepim-runtime and kdepimlibs 4.14.5 on top > of KDEPIM 4.14.2 as packages by debian and I still have most of the > issues. What do you mean by "compile on top of"? What sources are you using? I can find only 4.14.3 on kde.org, not 4.14.5. > And the Plasma 5 / Qt 5 port of KDEPIM is not yet ready as far as I am > aware of. Even that will use the Akonadi as we now it today, so it may > have still similar shortcomings and bugs. This means that parts of the KDE SC will use Plasma 5 / Qt 5, whereas other parts (KDEPIM) still use Plasma 4 / Qt4 ? Will that work? It sure wouldn't make sense to run Akonadi4 and Akonadi5 simultaneously.. ? Is Akonadi only used by KDEPIM? > I still use POP3 for my main private > account, but also IMAP is fragile, with Exchange, but there Exchange has > at least a fair share in causing the trouble. You mean Microsoft Exchange? > What could work quite well, and thats why I think for Munich it could > work, would be to have some decent (!) IMAP server like Dovecot (not > Exchange!) together with KMail. > So while for me KDEPIM and Akonadi got a lot better, like Nepomuk got, > before Vishesh replaced it by Baloo which works even better, KDEPIM and I > think especially Akonadi still has a fair share of issues. I think the > majority of the bugs I reported for KDE / Plasma in the last 2 or 3 years > with bugs.kde.org has been with Akonadi and KDEPIM. I see... > Yet, reporting those won´t magically make them go away and upstream could > need more developers. Thats why I hope that the adoption of KDEPIM for > Munich will help its overall stability. Cause frankly, from what I see so > far, it is not enterprise ready at all. > So for a clearly defined setup where you control server and client I think > for IMAP it can work okay. Not excellent, but okay. I use the mail server of my web hoster, and download the mail to my desktop system, using POP3 - no need for IMAP. It's simple this way. > In case you want to go that route, I suggest you also subscribe to kdepim- > users and probably kde-pim upstream mailinglists via lists.kde.org and be > prepared to deal with any issues you see, report bugs, help with bug > triaging and try to be patient. Yes, that's what it amounts to. Bye Volker -- To UNSUBSCRIBE, email to debian-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/15321979.eiy9pJ50aW@debian
