[pkg-kolab] Kolab debian repositories

[Diane Trout]

> Yes, the repositories are just revised packaging for the packages I had to
> (or chose to) change and then rebuild. For the other packages I used the
> OBS files and rebuilt using pbuilder. For reference, here are my
> repositories of packaging files:

Thank you for the pointers to all the repositories.

> 
> Nice! Especially the last bit with Dovecot and PostgreSQL. It would be
> interesting to hear of how you did that so that we might broaden the options
> for setting up Kolab. I can configure Dovecot to function as an IMAP
> server, but I haven't been able to really test it with Kolab or to
> integrate it properly.

For this round of experimenting I started with the kolab from source 
instructions. (http://docs.kolab.org/howtos/build-kolab-from-source.html). My 
current goal is to get the webdav sync working.

I'm not sure how useful the following story is, but I'll go ahead and share it 
for completeness.

First I set up roundcube using their instructions for working with Postgres. 
Dovecot just worked. Getting to viewing email was pretty easy.

Next I added in the roundcube-kolab-plugins and tried to get enough of the 
plug-ins working to show calendaring information. First I tried using the php-
kolabformant and php-kolab from the debian repositories, but those were too 
old and I had to use the obs versions. Then I had issues with needing the IMAP 
metadata extension and I had to upgrade to dovecot 2.2.10 from unstable. 

Once all of that was updated and I had to manually configure the subscriptions 
to the calendaring/contact folders in round cube and I used the manage folder 
ui to set what type of data was being stored in each folder type.

Once that was set I was able to see contacts and calendar entries created with 
kontact.

Up to this point I had avoided setting up an ldap server by commenting out 
kolab_auth.

Next I tried to set up chwala, using the readme in its source tree and 
discovered that does need an ldap server.

I setup openldap and copied over some minimal ldap records from a system setup 
with kolab 3.1. 

For the moment in kolab_auth I changed the kolab_auth_filter from objectClass 
kolabInetOrgPerson to inetOrgPerson as I didn't want to deal with needing to 
convert the schema holding the kolabInetOrgPerson.

Once I had those changes I was able to log in to chwala and upload a file. 
Though the files plugin in roundcube still isn't working yet.

Then I tried to setup iRony, and although I made some progress my mess of 
multiple git checkouts and symlinks splicing together plugins and plugin 
configuration files is getting too confusing to extend.

At this point I'm probably going to step back and try again using your 
packages for roundcube, roundcube kolab plugins, chwala and irony.

 
> P.S. Yesterday, I discovered that we might need to work on the Postfix
> integration, given that it didn't seem to be set up for secure
> communication, thus preventing the sending of mail. Again, advice from more
> experienced packagers and mail admins is very welcome.

I will try to share whatever progress I can make. My current observation is 
manual configuration is a better choice than setup-kolab if you're trying to 
use kolab components far outside their expected environment.

Diane