| 1 |
On Saturday 19 November 2005 01:07, Duncan wrote: |
| 2 |
> Barry.SCHWARTZ posted <20051119073425.GA22801@××××××××××××.org>, excerpted |
| 3 |
> |
| 4 |
> below, on Sat, 19 Nov 2005 01:34:25 -0600: |
| 5 |
> >> The system list will be in your profile, which is /supposed/ to be the |
| 6 |
> >> directory pointed to by the /etc/make.profile symlink. Normally, that |
| 7 |
> >> symlink will point to somewhere in the portage tree, under profiles, |
| 8 |
> >> which would mean a subdir of /usr/portage/profiles (typically |
| 9 |
> >> /usr/portage/profiles/default-linux/amd64/2005.1 or something similar), |
| 10 |
> >> if you haven't customized the path to your $PORTDIR |
| 11 |
My make.profile is fine. In fact I changed from 2005.0 to 2005.1 on both |
| 12 |
machines, with no effect on either. |
| 13 |
|
| 14 |
> >> |
| 15 |
> >> Assuming the symlink is pointing to the correct spot in your portage |
| 16 |
> >> tree, if the spot (or your entire portage tree) is somehow empty, an |
| 17 |
> >> emerge sync should correct the issue. |
| 18 |
> > |
| 19 |
> > Neh, I got the same problem. Seems sync with an outside server fixes |
| 20 |
> > the problem, so it must be a bug in my local rsync server, likely a |
| 21 |
> > semi-ubiquitous bug. |
| 22 |
> |
| 23 |
> Maybe. |
| 24 |
> |
| 25 |
> It's also possible there's a bad public rsync server. |
| 26 |
except that my local rsync master _has_ its system list. |
Archives