On Fri, 08 Jun 2012 21:28:19 +0200 Jarry <mr.ja...@gmail.com> wrote: > On 08-Jun-12 18:38, Nikos Chantziaras wrote: > >> I just noticed there is new stable portage-utils ebuild > >> (for amd64) but my system does not want to update it > > > > Is it in your world file? If not, either add it, or add > > "--with-bdeps=y" in the emerge command. > > This solves the issue, but it is strange: portage-utils are > not in my world file, so why are they installed? I suppose > this ebuild was maybe included in "system" at the time of > installation and later removed. But if it is so, why is > this "orphaned package" not uninstalled whenever I run > "emerge --depclean"?
It's not orphaned, and AFAIK portage-utils was never in @system. But pambase DEPENDs on portage-utils, do you have pambase installed? Portage's default behaviour is to ignore build-time deps for emerges and consider them for --depclean. This makes sense and avoids unnecessary compiles if an update is only required to build something else, not merely to run it. You appear to have hit this exact thing. "equery depends portage-utils" will tell you the depends, then you can look in each of those ebuilds to see what kind of dependancy it is. -- Alan McKinnnon alan.mckin...@gmail.com
