Really, this is sort of serious. I have sysklogd-1.4.1-r2 emerged, and NOT
metalog. metalog is NOT installed. however, I did a emerge -u world -p, hey, it
showed metalog marked for upgrade!
Thinkering about abit, I got this on emerge -s metalog
Latest version available: 0.6-r10
Latest version installed: 1.4.1-r2
hmm.. 1.4.1? hey! isn't that sysklogd?! emerge -s sysklogd..
Latest version available: 1.4.1-r2
Latest version installed: [ Not Installed ]
This is a pretty massive mixup. I've seen this in Gentoo 1.2 also, with older
portage than this (2.0.37).
It can suddenly start to behave this way after an emerge rsync, after being just
fine for a few weeks.
Verify this is still currently a problem.
Do you have /var/db/pkg/app-admin/sysklogd
Do you have /var/db/pkg/app-admin/metalog
Is there an entry in /var/cache/edb/virtuals for metalog or sysklogd
Portage version? (emerge -V)
Unmerge + Remerge sysklogd ---- fix it?
umerge sysklogd + emerge metalog --> Still same '-s' issue?
umerge metalog, remerge sysklogd -- Still have the problem?
I have unmerged metalog (well, it deleted sysklogd..), and remerged sysklogd a
while ago, and that fixed my problems. Since it's a while ago, i can not check
the other points you made. It seemed like an issue in moving sysklogd to another
category a while back(?).
Too old to be useful.