On Wed, Apr 30, 2008 at 11:00 AM, <[EMAIL PROTECTED]> wrote: > "Mark Knecht" <[EMAIL PROTECTED]> writes: > > > eix-sync > > eix-test-obsolete > > emerge -pvDuN --with-bdeps=y world > > emerge -p --depclean > > emerge -pvDuN --with-bdeps=y world > > revdep-rebuild -p > > eix-test-obsolete > > > > Assuming everything is totally clean, or at least understood, now I > > change the profile and repeat the above tasks. > > What does it mean or what is called for if eix-test-obsolete returns > hundreds of packages? > > Installed packages with a version not in the database (or masked): > > [U] app-admin/eselect ([EMAIL PROTECTED]/21/06 -> (~*)1.0.11-r1): Modular > -config replacement utility >
In general it means that the version of the package (eselect in this case) has been removed from the portage tree by the folks who maintain portage. That means that should you want or need that specific version you cannot get it from portage doing something like this: emerge -pv =app-admin/eselect-1.0.2 The general path I'm taking at this point is that all of these packages are out of date and should be updated. In general they will be with the emerge -DuN world operation. However when I run into a list that is that large I try to handle it in pieces: emerge -DuN system emerge -DuN gnome emerge -DuN mythTV etc., where I work through the list in a few steps instead of just one pass. (The above are just examples, not suggestions.) The issue here, and you're free to assume otherwise, is that I personally didn't want to switch profiles until I was completely clean as I wouldn't understand what changes were taking place due to the profile change and which were because I wasn't up to date anyway. - Mark -- gentoo-user@lists.gentoo.org mailing list
