Home Home > 2009 > 05 > 07 > Kolab on its way back
Sign up | Login

Kolab on its way back

May 7th, 2009 by

After a long time, with lots of not visible activity Kolab, the groupware server build with many known open source components, is slowly getting back into openSUSE. For a year or so it was not possible to use Kolab on openSUSE versions newer than 10.3. That was due to the move from openldap 2.3 to 2.4. The latter does no longer support slurpd as replication mechanism, but uses syncrepl instead. Hence, kolab had to be extended to be able to work with new replication protocol. After that the way the webclient horde was packaged, changed from (to make a long story short) 1 big package, to many small packages. This in preparation for horde4. Today, the following message was posted to the kolab-user e-maillist:

after a lot of tests on a virtual system I finally upgraded my
productive Kolab server to 2.2.1 with the Suse packages.

Now you should now, that kolab-2.2.1 was released about month in April 2009. Although we (Marcus Huewe, Alar Sing, and the author of this article) are not there yet, seeing this message means a lot to us. We’re making good process!

Both comments and pings are currently closed.

3 Responses to “Kolab on its way back”

  1. Shrenik

    Hey Richard,

    That’s great news. Will help with whatever I can to fast-track this. I have missing Kolab for a long time now as my architecture moved over to 10.3 and further.
    Do let me know if I there are any specific tasks listed apart from the usual testing and reporting bugs. May be I can be of some help.

    Cheers,
    Shrenik

  2. Shrenik

    Hey Richard,

    That’s great news. Will help with whatever I can to fast-track this. I have missing Kolab for a long time now as my architecture moved over to 10.3 and further.

    Cheers,
    Shrenik

  3. Richard

    Hi Shrenik,

    there is not something specific you can do to fast track kolab, at least as far as I can remember. Perhaps you can join the kolab-devel and kolab-users list, as problems about kolab on openSUSE are discussed there. Best thing you can do now is to test kolab on openSUSE intensively, especially the initial install (via zypper and yast), and to test the kolab freebusy functionality. It would also be good to test the webclient.

    Looking forward to your contribution!