From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GLjEo-0006ci-DC for garchives@archives.gentoo.org; Fri, 08 Sep 2006 16:29:54 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k88GRmol029405; Fri, 8 Sep 2006 16:27:48 GMT Received: from anli.goldspace.net ([80.246.67.229]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k88GIirC028143 for ; Fri, 8 Sep 2006 16:18:44 GMT Received: from localhost (localhost [127.0.0.1]) by anli.goldspace.net (Postfix) with ESMTP id 6C45B7FC77 for ; Fri, 8 Sep 2006 20:18:16 +0400 (MSD) From: Andrew Gaydenko To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Remerge the system with gcc-4.1? Date: Fri, 8 Sep 2006 20:18:16 +0400 User-Agent: KMail/1.9.4 References: <20060908070933.59450@gmx.net> <200609081926.35156@goldspace.net> <20060908170533.2d6bab87@hactar.digimed.co.uk> In-Reply-To: <20060908170533.2d6bab87@hactar.digimed.co.uk> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200609082018.16156@goldspace.net> X-Archives-Salt: d87a466f-aaec-4853-a698-05efa2b940f0 X-Archives-Hash: e8044ebefc1b27af08bf912f779e3bc2 I'm agree absolutely, I have switched to 4.1.1 already :-) Probably, it is not a bad idea to add a note about this trap somewhere in the official guide. ======= On Friday 08 September 2006 20:05, Neil Bothwick wrote: ======= On Fri, 8 Sep 2006 19:26:34 +0400, Andrew Gaydenko wrote: Honest to $DEITY, my mailer picked the tagline! > It is masked *now*, but it wasn't masked *before*, and unmerging was > not clean. I'm not the only who have lost plenty of time because of > this portage error. Yes, I specified that it's masked NOW. It may have caused you problems in the past (and many others, it's masked for a reason) but it is not a reason to avoid the GGC upgrade now. -- gentoo-user@gentoo.org mailing list