Re: heimdal and testing
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 working on getting ghostscript rebuilt with -O0 on sparc/hppa? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: heimdal and testing
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 it's going to need a hint from the release team, and it'll need to go at the same time as all packages that in testing depend on the old sonames (it's always been like this, so what you say in your other mail is not correct). 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... Once those failures are resolved, please remind us to track your transition by mailing to -release. Thanks, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Any life, no matter how long and complex it may be, is made up of a single moment: the moment in which a man finds out, once and for all, who he is. -- Jorge Luis Borges -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: heimdal and testing
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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: heimdal and testing
Le April 28, 2008 06:17:10 pm Brian May, vous avez écrit : 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-gs sapi-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? Yes. So heimdal is still waiting for cyrus-imapd-2.2 to be ready to transition. 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. It has never been like that. There can't be multiple versions of a source in a given suite simultaneously. The only way to workaround the impact when there are soname bumps is to have several source packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
heimdal and testing
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 http://bugs.debian.org/cgi-bin/pkgreport.cgi?ordering=normal;archive=0;repeatmerged=1;exclude=pending%3Afixed;exclude=pending%3Adone;package=kolab-cyrus-imapd, and kolab-cyrus-imapd http://bugs.debian.org/cgi-bin/pkgreport.cgi?ordering=normal;archive=0;repeatmerged=1;exclude=pending%3Afixed;exclude=pending%3Adone;package=kolab-cyrus-imapd is broken due to #411240 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411240 (shouldn't this be RC?) and a dependency on libkvm-dev http://release.debian.org/migration/testing.pl?package=libkvm-dev which is no longer in Debian. Is there anything I can do about this? Thanks Brian May -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: heimdal and testing
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 PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
