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
