Date: Fri, 23 May 2003 08:48:14 +0200 From: Jens Rehsack <rehsack@liwing.de> To: Kris Kennaway <kris@obsecurity.org> Cc: Dirk Froemberg <dirk@FreeBSD.org> Subject: Re: HEADS UP: Ports are now frozen Message-ID: <3ECDC42E.9040603@liwing.de> References: <20030523035931.GA44629@rot13.obsecurity.org> <3ECDBAB7.80005@liwing.de> <20030523062705.GA45408@rot13.obsecurity.org> <3ECDC1A4.6000502@liwing.de> <20030523064250.GA59823@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/23/2003 8:42 AM, Kris Kennaway wrote: > On Fri, May 23, 2003 at 08:37:24AM +0200, Jens Rehsack wrote: >> On 5/23/2003 8:27 AM, Kris Kennaway wrote: >> > On Fri, May 23, 2003 at 08:07:51AM +0200, Jens Rehsack wrote: >> >> On 5/23/2003 5:59 AM, Kris Kennaway wrote: >> >> > The ports tree is now frozen. Unauthorized committers will be fed to >> >> > Beastie. >> >> >> >> Hi Kris, >> >> >> >> I don't know how long it took until php 4.3.2 is released, but I >> >> strongly recommend to try to include the update of it into 5.1-RELEASE, >> >> because of the currently included one doesn't work well with the openssl >> >> included in the base system. You can take a look into PHP's bug database >> >> at http://bugs.php.net/?id=22809 for details. >> > >> > Sorry, that won't be possible..there just isn't time. >> >> How does such a situtation is managed usually? > > I'm not sure what you're asking. I ask how is a situation managed when a port patially breaks with the base system but the ports tree is frozen. Because of the new OpenSSL, mod_php4 in version 4.3.1 won't build with OpenSSL, but the upcoming 4.3.2 will do. The php-4.3.2RC4 is out and the 4.3.2-RELEASE will come in next 1-3 weeks. Can this port becomes committed whether the ports tree is frozen or not or should it marked as broken when OpenSSL is used? Jens
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3ECDC42E.9040603>