[pkg-horde] Current status of Horde 3.2 and Kolab 2.2 packaging

[Mathieu PARENT]

Hello,

I'm posting to both lists so that the two teams know about interactions.

The purpose of this mail is to help packaging horde 3.2 and kolab 2.2 for lenny.


First, about Horde.

Horde 3.2RC4 has been released. Horde 3.2 with all apps (IMP, Turba,
Kronolith, ...) will be released by the end of May (see [1]). I have
prepared packages :
- horde3 OK (ready for experimental):
  * removed files present in other packages (xinha, fckeditor,
libjs-scriptaculous, tinymce)
  * updated debian/copyright
- imp4 almost OK:
  * removed files present in other packages (libjs-scriptaculous)
  * TODO: debian/copyright
- others (dimp,ingo,kronolith,mnemo,nag,turba)
  * TODO: debian/copyright
  * TODO: update
  * TODO: test
I have also packaged xinha, which is waiting a mentor (see [2] and [3])

Can some people at pkg-horde-hackers help update/test/upload
''others'' packages ?


Then, Kolab:

I have packaged everything. This is good IMO. Only one wondering
([4]). Last thing is horde 3.2 which is needed for freebusy and
filter.


If you want to test the packages (horde/kolab), add "deb
http://pkg-kolab.alioth.debian.org/packages/snapshots unstable main"
to /etc/apt/sources.list.

NB: you have to run the 'newaliases' postfix command if you haven't before.

Thanks

Mathieu

[1]: http://marc.info/?l=horde-dev&m=121057898226828&w=2
[2]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479708
[3]: http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=xinha
[4]: kolabd calls kolabconf too often. This seems to comes from slapd
persistent searches triggering too often. This is not a regression.