Hi, I'm using portage-2.0.46-r2 and I get heavy troubles while searching for packages for instance. Here's a typical sample output of what I get : julien@infinity julien $ emerge search portage Searching... / aux_get(): (1) couldn't open cache entry for app-admin/portagemaster-0.1.8 Check for syntax error or corruption in the ebuild. - aux_get(): (1) couldn't open cache entry for app-admin/kportage-0.5.1 Check for syntax error or corruption in the ebuild. [ Results for search key : portage ] [ Applications found : 3 ] aux_get(): (1) couldn't open cache entry for app-admin/kportage-0.5.1 Check for syntax error or corruption in the ebuild. aux_get(): (1) couldn't open cache entry for app-admin/kportage-0.6 Check for syntax error or corruption in the ebuild. emerge: search: aux_get() failed, skipping aux_get(): (1) couldn't open cache entry for app-admin/portagemaster-0.1.8 Check for syntax error or corruption in the ebuild. aux_get(): (1) couldn't open cache entry for app-admin/portagemaster-0.2.0 Check for syntax error or corruption in the ebuild. emerge: search: aux_get() failed, skipping * sys-apps/portage Latest version available: 2.0.46-r2 Latest version installed: 2.0.46-r2 Size of downloaded files: 143 kB Homepage: http://www.gentoo.org Description: Portage ports system julien@infinity julien $ Doing a emerge sync resolves the problem, it seems to get in a mess after emerging any ebuild. This kind of bug is really annoying ... I'm running a fresh install using the latest live cd. Everything's fine apart from that. Thanks a lot for your great work :-)
So are you saying this is gone after an rsync update?
Exactly. It goes away after your sync. Regards.
It's due to updating portage before the metadata is updated. Not something that's a bug or really fixable. I'll see about having the metadata cache updated earlier next time.
