Barry.SCHWARTZ posted <20051119073425.GA22801@...>, 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.
>> 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.
It's also possible there's a bad public rsync server. A few months ago, I
got one that was caught up on most things but for some reason wasn't
syncing a particular package (just one I saw, perhaps more, but not the
whole server). Every time I'd hit that server, the package I had merged
(and that was a dependency of something else) would disappear, and portage
would want to downgrade it (several versions, in fact), but then say there
weren't any packages matching the dependency and want to unmerge the whole
The first time, I filed a bug on the "leaf" package in question, saying
the dependencies had been removed. The gentoo maintainer said no, they
were there, and sure enough, after resyncing they were!
Needless to say I felt a bit foolish for having filed the bad bug, but
soon enough, I hit the same server, and had the same thing happen again!
Only this time I knew the package WAS still in the tree, so it could only
mean one thing: the rsync server was bad!
Fortunately, I was able to track down which server it was and file an
infra/mirrors bug. Checking for dups before filing it, I could see that
that particular server had been taken out of rotation a few months
earlier, due to connectivity issues. (IIRC it was moved on the LAN,
probably to a new subnet with a different IP, and the firewall rules
hadn't been updated.) They had fixed them and were back in rotation, but
for some local config issue, probably a permissions issue on their rsync
daemon such that it couldn't write to a particular subdir or something,
that particular package hadn't updated since before the connectivity
issues started. It was nearly a year out of date on that particular rsync
server, but ONLY that particular rsync server!
IIRC it took the local server contact three days to respond, not too bad,
actually, and another day or so to track down and fix the issue, and
resync with the master.
So anyway... such things do happen, and with two of you reporting a
similar issue, I wouldn't be surprised if you both happened to sync off
the same defective public rsync server, which happens to be missing that
particular profile, or at least the system list from it.
(Note that I didn't mention which one it was in my case. That has been
awhile, and those guys do donate a /lot/ of bandwidth and some hardware as
well. One's bound to go out once in awhile, and I doubt yours is the same
one I had issues with back then, so no reason to name it. I would of
course if it were a current problem.)
You should be able to check your emerge.log and see who you synced with
that time. I'd suggest checking it out and filing a bug if it's still a
problem (I verified mine by manually checking with a web browser) and
there aren't others filed on it yet.
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
email@example.com mailing list