On Saturday 19 November 2005 01:07, Duncan wrote: > Barry.SCHWARTZ posted <[EMAIL PROTECTED]>, excerpted > > below, on Sat, 19 Nov 2005 01:34:25 -0600: > >> The system list will be in your profile, which is /supposed/ to be the > >> directory pointed to by the /etc/make.profile symlink. Normally, that > >> symlink will point to somewhere in the portage tree, under profiles, > >> which would mean a subdir of /usr/portage/profiles (typically > >> /usr/portage/profiles/default-linux/amd64/2005.1 or something similar), > >> if you haven't customized the path to your $PORTDIR My make.profile is fine. In fact I changed from 2005.0 to 2005.1 on both machines, with no effect on either.
> >> > >> Assuming the symlink is pointing to the correct spot in your portage > >> tree, if the spot (or your entire portage tree) is somehow empty, an > >> emerge sync should correct the issue. > > > > Neh, I got the same problem. Seems sync with an outside server fixes > > the problem, so it must be a bug in my local rsync server, likely a > > semi-ubiquitous bug. > > Maybe. > > It's also possible there's a bad public rsync server. except that my local rsync master _has_ its system list.
pgpDFqyP9pRSn.pgp
Description: PGP signature
