On Tue, Apr 29, 2008 at 06:08:06PM +0200, Adeodato Simó wrote:
Anyway, the first problem is that cyrus-imapd-2.2 is not built on all
arches yet:
http://buildd.debian.org/~jeroen/status/package.php?p=cyrus-imapd-2.2
Sounds like problems with ghostscript...
Yes, precisely that.
Is anyone
Hello,
Hello Brian. For these kind of questions, I don't mind if you main the
-release list directly.
Can somebody please interpret why Heimdal is blocked from testing for me:
http://release.debian.org/migration/testing.pl?package=heimdal
The version of heimdal in unstable bumps sonames, so
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
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
Hello,
Can somebody please interpret why Heimdal is blocked from testing for me:
http://release.debian.org/migration/testing.pl?package=heimdal
As far as I can tell, it won't get installed because that would break
kolab-cyrus-imapd
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.
--
To UNSUBSCRIBE, email to [EMAIL
6 matches
Mail list logo
