Created attachment 529134 [details] emerge --info Hello. Steps to reproduce: 1. emerge -s codec OR emerge -s "codec" Expected results: 1. media-libs/nv-codec-headers is among the search results Actual results: 1. media-libs/nv-codec-headers is NOT among the search results using either emerge -s codec OR emerge -s "codec" Additional info. Portage knows about the package: $ equery list -p -o nv-codec-headers * Searching for nv-codec-headers ... [-P-] [ ~] media-libs/nv-codec-headers-8.1.24.1:0 P.S. What is 'simple search' mentioned in emerge man under `--search' option desc?
Created attachment 529136 [details] emerge -s codec
It works for me. Maybe you have a stale pkg_desc_index located at $(portageq get_repo_path / gentoo)/metadata/pkg_desc_index?
(In reply to Zac Medico from comment #2) > It works for me. Maybe you have a stale pkg_desc_index located at $(portageq > get_repo_path / gentoo)/metadata/pkg_desc_index? nv-codec-headers is indeed missing from thar file, so I guess it's stale. I surely didn't touch it manually. Does portage handle it automatically?
(In reply to Coacher from comment #3) > (In reply to Zac Medico from comment #2) > > It works for me. Maybe you have a stale pkg_desc_index located at $(portageq > > get_repo_path / gentoo)/metadata/pkg_desc_index? > nv-codec-headers is indeed missing from thar file, so I guess it's stale. > I surely didn't touch it manually. Does portage handle it automatically? It's never generated automatically, somebody has to run this command: egencache --update-pkg-desc-index --repo=gentoo
I see. I usually get a fresh copy from https://github.com/gentoo-mirror/gentoo I guess it's not a portage problem then. Sorry for the noise.
