On Mon, Mar 03, 2003 at 04:47:49PM -0300, Norberto Bensa wrote: > Which kind of "weird errors"? I'm exporting /usr/portage since months ago > without any error at all; except for some permission issues after I upgraded > to portage 2.0.47-r7 (fixed running /usr/sbin/pwconv and /usr/sbin/grpconv.)
My apologize for not being very specific, as I couldn't I don't honestly know exact details (it was quite some time ago). I remember at the time I attributed them to being a difference of information contained in files from /var/cache/edb (not nfs shared) and the portage tree (nfs shared). When the tree was updated on one machine it seemed as though the files in /var/cache on other machines were not updated, and from what I remember caused odd dependency problems (emerge tried to pull in dependencies from the dep cache that no longer existed in the ports tree). The good news is that with a newer portage (portage-2.0.47-r8 at the moment) I cant seem to replicate the problem, and things seem to be running well with a full export of portage over nfs. Anyone with better knowledge of portage have an idea how things in /var/cache/edb if not synced with what is actually in the portage tree could do for a situation like this ? or is it that emerge rsync is not the only thing that updates those files. -- Douglas Peter Sculley GnuPG key available at www.usal.us
pgp00000.pgp
Description: PGP signature
