On 9/9/19 11:16 AM, Peter Humphrey wrote:
On Monday, 9 September 2019 15:52:23 BST Jack wrote:
What does "eix most' show?
$ eix -e most
[I] sys-apps/most
Available versions: 5.0.0a-r1{tbz2} ~5.1.0
Installed versions: 5.0.0a-r1{tbz2}[1](14:18:39 22/03/19)
Homepage: https://www.jedsoft.org/most/
Description: Paging program that displays, one windowful at a
time, the contents of a file
[1] "prh-local" /usr/local/portage
(What ugly sentence construction.)
Man eix says that eix-test-obsolete is a script that calls eix several times,
so I'd have been surprised if its output had differed from eix's.
True - I just wanted to confirm it didn't think there were any ebuilds
other than in the main tree.
It looks like portage thinks your current install of most was done from
your local repository, Either that's true, and you just deleted it
from /usr/local/portage, or else portage is confused about where it
last installed from. In either case, just "emerge -1 most" and it
should (re)install it from the main tree.
It's never been in my local repository. Emerging it again has fixed the eix
database though.
If you never had that package in your local repo, perhaps the more
important question is why did portage think you did?
Indeed, and that's what I can't work out. As far as I can remember, the only
local ebuilds I've had are grub-legacy, on that same box, and a patched
version of localepurge to make it obey the --silent option. I still have grub,
but not localepurge because it's been dropped from Gentoo.
Have you added or deleted any repositories lately? This is just a wild
guess (and likely wrong) but I wonder if the eix database uses an index
into the list of repositories instead of text reference. Doesn't seem
likely, or there probably would have been other entries pointing to a
"wrong" repository. Check out eix-installed to see if you can find any
other anomalies.
