From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NFrBo-0001HE-JD for garchives@archives.gentoo.org; Wed, 02 Dec 2009 15:32:24 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3BBC3E0603; Wed, 2 Dec 2009 15:31:45 +0000 (UTC) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by pigeon.gentoo.org (Postfix) with ESMTP id D9C02E0603 for ; Wed, 2 Dec 2009 15:31:44 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id e21so270780fga.10 for ; Wed, 02 Dec 2009 07:31:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=vqPUwn8zU6+GgPNnculMCkAc9+jnkoGItUBKuC6ib6U=; b=N7u4huBMD9bwm0rkdsT0ESH/hgq+5HdjJIdIH5GBWhp/Il9CdnewjJg9cKBHQxEd+Q f8P0xKL94RRXXhD4Fi8y0FsQpwCb0fwrsOGlRvaMkwbeiF5x+tNiaTNLVI83hUwTpZRF Fqr2A1f/MnqDrMQAWCYzMtmYzosCIfAO9gBNk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; b=DaV9Ft1JmL9jHWQumS9a4/FixbcuaTQLECURuwcA7SdBWk/M4GLtXmeW2j/vNZd1+A mLesVWs0Gvm6Ij8yyeoAHRykxht0JJcTqP1DWnfuAus9Lm+l6802fLbQdYDm7CDL5Wp4 KU0xW2dz86Rl11V1ZXi3hF5iuh3DmJ1SpMXS0= Received: by 10.216.88.139 with SMTP id a11mr84146wef.50.1259767904214; Wed, 02 Dec 2009 07:31:44 -0800 (PST) Received: from nazgul.localnet (dustpuppy.is.co.za [196.14.169.11]) by mx.google.com with ESMTPS id i6sm2824011gve.1.2009.12.02.07.31.42 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 02 Dec 2009 07:31:43 -0800 (PST) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Heads up: Your system might be broken and/or insecure due to serious patch-2.6 bug Date: Wed, 2 Dec 2009 17:30:37 +0200 User-Agent: KMail/1.12.3 (Linux/2.6.31-zen8; KDE/4.3.3; x86_64; ; ) References: <20091202144816.GA4798@ca.inter.net> In-Reply-To: <20091202144816.GA4798@ca.inter.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912021730.37356.alan.mckinnon@gmail.com> X-Archives-Salt: 312de6aa-0226-42e8-8f5e-01f1e8ade69b X-Archives-Hash: a8e21f13602a7522ca445b2024f294a2 On Wednesday 02 December 2009 16:48:16 Philip Webb wrote: > 091202 Nikos Chantziaras wrote: > > On 12/02/2009 12:51 PM, Alan McKinnon wrote: > >> On Tuesday 01 December 2009 18:02:48 Nikos Chantziaras wrote: > >>> Everyone should read the following and follow the advice given: > >>> http://blog.flameeyes.eu/2009/12/01/gentoo-service-announcement-keep-cl > >>>ear-of-gnu-patch-2-6 > >> > >> I emerged patch-2.60 when it hit ~amd64 then downgraded it 10 days later > >> when a report on b.g.o. showed it was affecting OOo. > >> Right in the middle of those 10 days, I ran 'emerge -e world' > >> > > > > Yep, this bug was a major annoyance for me too. > > I emerged patch-2.6 on November 15 > > and since then, being on ~amd64, a *lot* of other packages. > > After downgrading, I needed to rebuild about 300 packages, > > including all of KDE4, Qt, Firefox and OpenOffice. > > Quite amazing how much damage a bug in a small package like this can have > > on a source-based distro... > > 2 pieces of advice to avoid such problems: > (1) never use the 'testing' versions of system pkgs; > (2) never run 'emerge world' without the '-p' flag. Balls. Neither of those will fix anything and they are not even feasible for this. I run ~amd64 for a reason, I want it that way. There is no known way to run amd64 for @system and ~amd64 for @world and still retain one's sanity. Of course I ran emerge -p. Well actually I run emerge -a but the effect is the same - see what's going to be installed before it's installed. Until a week ago no-one knew the effects patch-2.6.0 would have so when it appears in the list there's no reason to not proceed. Running amd64 isn't an option for me - this isn't one of my critical servers, it's my bleeding edge notebook and I like it the way it is. If I wanted to avoid problems like this I'd be using Ubuntu LTS instead. I'm not whinging about patch. I run ~amd64 precisely to help detect such things. I'm miffed at my own bad luck - the first emerge -e world I've had to do in two years and I just happen to have done it in the two week window about this package. Most folk now have to rebuild 70 - 300 packages, I'm stuck with potentially 1472 -- alan dot mckinnon at gmail dot com