From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vms040pub.verizon.net (vms040pub.verizon.net [206.46.252.40]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j3LBbES5008948 for ; Thu, 21 Apr 2005 11:37:14 GMT Received: from vmware.local.domain ([65.169.92.10]) by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix 0.04 (built Dec 24 2004)) with ESMTPA id <0IFA001BSOA75O31@vms040.mailsrvcs.net> for gentoo-dev@lists.gentoo.org; Thu, 21 Apr 2005 06:37:20 -0500 (CDT) Received: by vmware.local.domain (Postfix, from userid 1000) id 219EB91A2E; Thu, 21 Apr 2005 06:37:18 -0500 (CDT) Date: Thu, 21 Apr 2005 06:37:17 -0500 From: Paul Varner Subject: Re: [gentoo-dev] New apache stuff in testing -> please package.mask it In-reply-to: <200504210548.29928@zippy.emcb.local> To: gentoo-dev@lists.gentoo.org Message-id: <1114083437.6170.3.camel@vmware.local.domain> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-version: 1.0 X-Mailer: Evolution 2.0.4 Content-type: text/plain Content-transfer-encoding: 7bit References: <200504210548.29928@zippy.emcb.local> X-Archives-Salt: 7974a67e-b131-45a6-ae18-d50ec7b0591d X-Archives-Hash: 12c932c70fdb21298ceb64b3e5a6b249 On Thu, 2005-04-21 at 05:48 +0100, Elfyn McBratney wrote: > I've filed a bug[1] requesting that ebuilds with updated apache stuff > (anything using the new apache-module or depend.apache eclass/the new install > layout) be package.mask'd due to the regressions and breakages in testing. I > may have missed packages in the bug, hence this mail - you know best if your > using new stuff. :) > > Please package.mask said ebuilds ASAP so we can get apache itself into > package.mask. Even though I stated my opinion that I would like to see the new changes package masked again, the consensus that I read on the thread disagreed with that approach. My unsolicited opinion based upon the previous thread is since it is already out of the bag, leave it in ~arch and actively work the bugs so that you can get it to the point of being able to mark it stable. Regards, Paul -- gentoo-dev@gentoo.org mailing list