[pkg-kolab] pkg-kolab-devel Digest, Vol 81, Issue 1

Paul Klos kolab at klos2day.nl
Thu Apr 11 15:50:25 UTC 2013

Neil Price schreef op 11-04-2013 12:39:
> On 10/04/2013 20:48, Soren Stoutner wrote:
>> I listen to the list, although I don't post much.  I run several 
>> production Kolab servers based on the existing Debian packages.  I am 
>> very interested in the work that is being done to package the newer 
>> versions of Kolab for Debian.  I typically do not install packages 
>> from third party repositories on my production server, so I am waiting 
>> for these packages to make it into Debian testing.  I am hopeful that 
>> there will be an upgrade path from the existing Debian packages so 
>> that it doesn't wipe out my existing settings and stored IMAP mail, 
>> but I imagine there are some difficulties in doing so.

Good to see that people are interested!

The libraries we're currently talking about are required to get 
kontact/kmail Kolab-enabled on Debian. This is obviously 
client-oriented, and still a long way from being able to install a Kolab 
3 server on Debian, from Debian repositories.

That said, I can understand not using 3rd party repositories on 
production systems, so I suppose we shouldn't stop at libkolab* :-).

As to upgrade paths, there is official documentation:

There are tools to migrate mails from an old Kolab 2 to a new Kolab 3 
server, along with upgrade tools for the new Kolab XML format. There's 
no documented in-place upgrade from Debian packages; I have no idea if 
that would work at all, but somehow I doubt it...

> I'm in pretty much the same position but with the added complication
> that I use the same ldap for a lot other things so the change to a new
> ldap backend would probably be traumatic.
LDAP is where things start to hurt, at the moment. Kolab 3 currently 
has a hard dependency on 389 Directory Server, which is a bit of a 
strange beast in the Debian world, which doesn't help. People use their 
existing LDAP servers for a host of stuff, and rightly so, but that does 
tend to complicate things. You might wanna check kolab-devel and 
kolab-users (see http://kolab.org/community), if you're not already 
doing so, as that's where these types of discussions are going on.



More information about the pkg-kolab-devel mailing list