Hi Jens, Am Donnerstag 18 August 2011, um 13:06:26 schrieb jens: > Hello Christian, > > > Le mercredi 17 août 2011 à 10:55 +0200, Christian Hilberg a écrit : > > Hi jens, > > > > Am Mittwoch 17 August 2011, um 08:42:36 schrieb jens: > > > Your evolution-kolab plugin version 0.2.1 compiled without problem on > > > my debian 6 squeeze. > > > > Nice to know. :) > > For further tests I compiled a debian squeeze package. > I had to adjust 4 file from the dedian (ubuntu) packaging descriptions > files. You will find them attached to this. It is not properly done > though, because I manually changed configure.am file which should be > done by patch in the debian directory. If anyone is experienced in > packaging, please tell me how to do it. As time permits, I'll look into this. Thank you for your efforts! > > > Unfortunately it does not connect properly to my citadel-server, > > > because it can probably not identify > > > the right folders (see attached screen-shot and debug log). > > > > There might be several things involved here. First, the log shows lines > > like > > > > CRITICAL **: categories_icon_theme_hack: assertion `filename != NULL && > > *filename != '\0'' failed > > > > and subsequent GTK assertion failures. This has nothing to do with the > > evolution-kolab plugin really, but GUI assertion failures mean that the > > whole application is not guaranteed to be in any consistent state any > > longer. This may cause any kind of errors which are hard to isolate > > then. > > I have no idea where these errors come from. Maybe my ~/.evolution > directory is too old and contains data from previous evolution versions. Since evolution-kolab has not matured very much, it is a good idea to start out with a clean environment for testing, i.e. it may be worth it to create a new user and then try evolution-kolab with this user. > > Secondly, please make sure to quit Evolution and start it again after > > setting up the Kolab account once. > > I tried but it did not help (see screen-shots and log file). Again, as time permits, I'll be looking into this. > > Third, we have never tested evolution-kolab against the Citadel > > implementation. Everything is quite fresh still, and we have a number of > > issues open with evolution-kolab running with Kolab 2.2.4 , which is the > > platform we've developed against. Your guess regarding the Folder types > > might be right. Kolab 2.2.4 implements draft-05 of the ANNOTATEMORE IMAP > > extension, which is used by evolution-kolab (and other Kolab clients) to > > tell the folder types apart. > > > > > The calendar code seems to work: I am able to create and to view > > > events. > > > > Nice! > > I can not tell if citadel implements raft-05 of the ANNOTATEMORE IMAP > extension, but I remember that I had to choose "imap+" during my mail > accout setup. The "kolab2" email part is based on "imap+". If switching from "imap+" to "kolab2" as email account (provider) type does not work, then something is really hosed there... If an IMAP server does not support the ANNOTATEMORE IMAP extension at all, then the "kolab2" account type should just show all IMAP folders. Support for the exact draft version (05) of the ANNOTATEMORE draft IMAP extension is critical for operation of evolution-kolab. If any other version of ANNOTATEMORE (or even the METADATA RFC, which is what ANNOTATEMORE finally resulted in) is implemented in the IMAP server, then there is no telling of what will happen, it has not been tested yet at all. > Unfortunately I do not have access to any native kolab server to do any > further tests. I tried to setup one on debian 6 server once, but even > after 1 day I did not manage to access the imapd and finally gave up. > > Citadel you just install and it runs without any configuration. I'm afraid there is currently no much gain in trying evolution-kolab with citadel, unless its compatibility level with Kolab 2.2.4 is really, really high. > > Maybe first try to get rid of these GTK assertion failures (seems like > > there is an issue with the windowmanager theme you're using). Next, > > configure everything for evolution-kolab according to the manual, run > > Evolution, wait, then quit Evolution and start it again. > > > > evolution-kolab is currently not showing good performance, it is rather > > slow. We're working on that. It might be wise not to test > > evolution-kolab against an account which has many entries yet. Also, > > please note that it is not yet advisable to use evolution-kolab in > > critical environments. > > I have to suspend my activity on this now, but I am still interested in > your project. Debian squeeze binaries/repository would be nice! We are heading towards this, but due to limited resources, cannot provide them presently. Just check in now and then, there may be progress with this in future. > I wish you a good continuation of this promising project! Thanks, Christian -- kernel concepts GbR Tel: +49-271-771091-14 Sieghuetter Hauptweg 48 D-57072 Siegen http://www.kernelconcepts.de/
Attachment:
signature.asc
Description: This is a digitally signed message part.