[pkg-kolab] no Kolab in Debian testing/Lenny?

[Mathieu Parent]

hi,

2009/1/3 Jürgen Büchs <Juergen.Buechs at gmx.de>:
> Hallo all,
>
> I've just recognized that there is no kolabd package in Debian testing.
> There's only version 1.9.4 in stable and 2.2.0 in unstable.
Yes, kolab won't be in lenny (more info here:
http://lists.debian.org/debian-release/2008/09/msg01211.html).

>
> So my question is:
> What will happen, when Lenny is released and I will upgrade my server?
>
> Will the old Etch version stay on the server or will it be removed?
> Shoudn't there be at least the old version included in Lenny?
The old version will stay on the server. But it won't work because
slapd in lenny is version 2.4 that doesn't include slurpd replication.
And Kolab lower than 2.2 requires slurpd.

>
> Or is it an option to ask for an "unblock request" for all the kolab packages
> to bring 2.2.0 into testing as there are no RC bugs?

I think you shouldn't do this, we want to release lenny! Don't bother
the release team with unblock requests.

Unblocking kolab requires unblocking libnet-ldap-perl which is a major
package with lots (33) packages depending on it. The release team
won't accept that.

The current right way to use 2.2 is to do apt-pinning
(http://www.argon.org/~roderick/apt-pinning.html) for *kolab* and
libnet-ldap-perl unstable packages.

>
> Looking to the Debian PTS, it seems to me that 2.1.0 was already in testing,
> but removed on 2008-10-02. Also 2.2.0 was not added, as 2.1.0 was removed
> before. PTS tells that the package has to be added, not updated.

It was removed as requested in the thread
http://lists.debian.org/debian-release/2008/09/msg01211.html. The
packages were not uploaded before the freeze. This is the rule and
kolab is not such a major package that justify to ignore the rule (see
the rules here:
http://release.debian.org/emails/release-update-200808).

>
> Please tell me also, if I should open a ticket for this in BTS.
Nope ;)

>
> As the deep freeze is coming soon we should act immediatelly, if something has
> to be done.
We are already in freeze. And the rules deny us already to do anything
for lenny.

To conclude, we missed the target for several reasons IMHO:
- it was not possible to keep 1.9.4 because slurpd was not in lenny
- 2.2.0 was released (July 11th) just before the freeze (July 27th),
- I had to add syncrepl support to kolab
(https://www.intevation.de/roundup/kolab/issue1755, first version mid
June, landed just after 2.2.0)
- we needed horde 3.2 which was released/uploaded just before the
freeze (2008-06-18)
- I'm not (yet) a DD, so this takes some time to upload new versions.

So it was near-to-unreachable as all those prerequisites were done
just before the freeze.

To reduce the impact, I encourage to use apt-pinning (backport is IMO
not needed as these are not compiled in packages).

>
> Best regards
>
>
> Jürgen Büchs
>
Regards

Mathieu Parent