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 BCDE0138247 for ; Thu, 9 Jan 2014 14:35:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 24F3FE0BDE; Thu, 9 Jan 2014 14:35:23 +0000 (UTC) Received: from smarthost01a.mail.zen.net.uk (smarthost01a.mail.zen.net.uk [212.23.1.1]) by pigeon.gentoo.org (Postfix) with ESMTP id 19705E0BCC for ; Thu, 9 Jan 2014 14:35:21 +0000 (UTC) Received: from [82.69.80.10] (helo=wstn.localnet) by smarthost01a.mail.zen.net.uk with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1W1Ghd-0001db-7P for gentoo-user@lists.gentoo.org; Thu, 09 Jan 2014 14:35:21 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Confusion about slot conflict Date: Thu, 09 Jan 2014 14:35:20 +0000 Message-ID: <1484578.SnrQb9Dyeh@wstn> Organization: at home User-Agent: KMail/4.11.2 (Linux/3.10.25-gentoo; KDE/4.11.2; x86_64; ; ) In-Reply-To: <1431205.NJSxqFsAsX@wstn> References: <52CB058D.2040301@gmail.com> <1431205.NJSxqFsAsX@wstn> 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-Originating-smarthost01a-IP: [82.69.80.10] X-Archives-Salt: 9d2580a0-22dc-4bc8-b192-b3543859e5b6 X-Archives-Hash: 74be7c94961ea4ac0c141bc7965fc313 On Wednesday 08 Jan 2014 12:31:52 I wrote: > I'm having a similar problem on my local LAN server, an Atom box. I sync > daily, and I've just synced again to make sure (31000 files, yet again, > nearly all in metadata). > > The Atom's packages directory is NFS-mounted in a 32-bit chroot on my > workstation, which does all the compiling work and then the Atom installs > from packages. > > For several days I've been finding that the Atom box throws up the libpng > error whereas the chroot doesn't want to upgrade anything. I've checked > that /etc/portage/* is identical except for make.conf, which has to differ > in proxy names, rsync hosts and a couple of other details. There's no > ACCEPT_KEYWORDS entry in either make.conf. > > The packages that portage complains of are all at the same versions on the > two boxes. > > I can't see a way out of this, other than forcing a libpng update on the > atom. Any further thoughts anyone? I'm almost sure I'm overlooking > something but in my present befuddled state I can't see what. Having tried many times to emerge -uaDvNK world on the Atom box and then separately emerging all the packages complained about, I finally got portage to come up with a set of packages to update - 637 of the total 645! While it's doing that (may be gone some time) I find that the /etc/portage directory on the Atom box had permissions root:root 0700. How that happened I've not the foggiest idea, but portage will have been unable to read any of the files in there. So, a word to the wise: beware rogues setting bad permissions. -- Regards Peter