[pkg-kolab] State of debian packages?

[Benoit Mortier]

Le Jeudi 15 Mars 2007 21:18, Philip Hands a écrit :
> Hi Folks,
>
> I've been intermittently trying to get kolab up and running for ages, but
> not quite making it for one reason or another, so rather than using the
> debian packages I thought I'd go for what as a Debianite strikes me as
> second-best, and install using OpenPKG -- which just worked.

Hello,

i personnaly use the debian etch version on several servers.

> OK, so I could try to work out what's different, but since I used the
> 2.1rc1 version, that will presumably be another OpenPKG install of an
> older version, and to be honest, I cannot be bothered because 2.1rc1
> supports multiple domains, whereas the debian packaged version is old
> enough not to, and that seems like a feature I need.
>
> On the other hand, I'm still not happy with moving to a mail system that
> is relying on something other than native Debian packages.

Mee too, i i'am currently planning on starting to work on the 2.1 kolab 
packages, some customers needs it.

> So, what's the current status of this stuff -- it strikes me that not
> much has happened of late, and I cannot say I'm all that surprised since
> it is apparently uninstallable at present (at least I've managed to waste
> several man days not getting a working system out of it a few times -- my
> current failure is falling over because it seems impossible to persuade
> it to deliver local mail *shrug*)

if you got those kind of problems just remove the line transport in main.cf 
of postfix

> There are also some other odd little wrinkles going on that make me think
> that if anyone is actually using this stuff, they are doing so by
> cheating, with local repositories.
>
> For example, kolabd depends on postfix, but debian's postfix doesn't yet
> include the leaf patch from kolab, so it doesn't really satisfy kolabd's
> requirements -- are the people using these packages just recompiling
> their own postfix binaries and putting them up on a local repository?  or
> are they not worrying about the lack of the patch? or is nobody actually
> managing to use the Debian packages at all?

I don't worry about the patch missing ;-)

> Also, if I'm going to put effort into getting this to a point where I can
> use it, it strikes me that it would be a lot more productive to work on
> the 2.1rc1 code, since any patches we might need in kolab are much more
> likely to be accepted into the trunk than an old release.  The fact that
> the SVN for pkg-kolab seems to be stuck at the 1.9.4 kolabd version makes
> me think that this effort has stalled -- is that right?  or are people
> beavering away but not mentioning it here?  or is something else going
> on?

1.9.4 = 2.0.4 ;-)

> If this is still a vaguely viable effort, I'm happy to add my shoulder to
> the wheel, but if it's died the I might as well spend my time more
> usefully elsewhere.

i will gladly accept your work with us on this matter, and you will see on 
the kolab mailing list that other people started to work on this also

cheers
-- 
Benoit Mortier
CEO
www.opensides.be
Contributor to Gosa Project : http://gosa.gonicus.de/
Contributeur to Nagios Plugins : http://nagiosplug.sourceforge.net/