Re: heimdal and testing

[Brian May <brian@microcomaustralia.com.au>]

Filipus Klutiero wrote:
> One of the things you could do is wait one day, after which
> cyrus-imapd-2.2 would be old enough to transition. cyrus-imapd-2.2
> needs to be updated, otherwise cyrus-common-2.2 would become
> uninstallable due to its dependency on libkrb5-22-heimdal in testing.
>
>
Another day, and nothing happened. I can't help think it is more
complicated then that.

<http://release.debian.org/migration/testing.pl?package=cyrus-imapd-2.2>
 says cyrus-imapd is now 10 days old and is waiting for Heimdal.

e.g. have a look at
<http://release.debian.org/migration/testing.pl?package=libsasl2-modules-gssapi-heimdal>.

Then this is only one day old
<http://release.debian.org/migration/testing.pl?package=kolab-cyrus-pop3d>.

It seems like Heimdal can't get moved unto testing until every package
that links against the libkrb5 also gets moved into testing, and these
have to be moved at the same time Heimdal is moved. Am I correct?

I thought the rules were that libkrb5-22-heimdal (and the corresponding
source) would remain in testing until is is no longer used by testing.
As such a Heimdal source package that only build libkrb5-24-heimdal
could still enter testing without updating all users of the library at
the same time. Maybe this has changed.

Brian May