From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id A4E0E1381F3 for ; Wed, 11 Sep 2013 11:57:38 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6E8B6E0CD8; Wed, 11 Sep 2013 11:57:33 +0000 (UTC) Received: from mail.ukfsn.org (mail.ukfsn.org [5.9.116.23]) by pigeon.gentoo.org (Postfix) with ESMTP id 4BAB0E0B88 for ; Wed, 11 Sep 2013 11:57:32 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.ukfsn.org (Postfix) with SMTP id 15B26DC14E5 for ; Wed, 11 Sep 2013 12:57:30 +0100 (BST) Received: from wstn.localnet (78-32-181-186.static.enta.net [78.32.181.186]) by mail.ukfsn.org (Postfix) with ESMTPS id 5BA8EDC10FC for ; Wed, 11 Sep 2013 12:57:29 +0100 (BST) From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Portage 2.2.1 stabilized? Date: Wed, 11 Sep 2013 12:57:28 +0100 Message-ID: <1848421.iGRMY2xNAI@wstn> Organization: Retired software quality manager User-Agent: KMail/4.10.5 (Linux/3.10.7-gentoo; KDE/4.10.5; x86_64; ; ) In-Reply-To: <52305096.7090002@libertytrek.org> References: <522DD0A1.5010207@libertytrek.org> <1823961.b6Gd6v5fYI@wstn> <52305096.7090002@libertytrek.org> 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-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Wed Sep 11 12:57:30 2013 X-DSPAM-Confidence: 0.9899 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 52305aaa46969397175846 X-Archives-Salt: 1acc59d7-ba6a-4b70-a31b-8666eaaeb009 X-Archives-Hash: e6823a5af0bf40edb89f37968736d000 On Wednesday 11 Sep 2013 07:14:30 Tanstaafl wrote: > Well, according to that bug, the fix is IN 2.2.1 (well, it says the fix > is in 2.1.13 and 2.2.0_alpha189, which means it is (should be?) in 2.2.1... > > So it can't be this bug? Whether that's true or not, I've found the problem. It was my own fault (so, what else is new?) I have a separate partition for /var/tmp and I'd forgotten to set the permissions. I don't know why it ever worked before. It should be fine now that I've set perms 1777. Sorry to cause you palpitations, Dale. Portage wasn't at fault - I was! -- Regards, Peter