On Thu, Dec 23, 2010 at 8:29 AM, Kevin O'Gorman <kogor...@gmail.com> wrote: > > > On Wed, Dec 22, 2010 at 9:04 AM, Mark Knecht <markkne...@gmail.com> wrote: >> >> On Wed, Dec 22, 2010 at 8:36 AM, Kevin O'Gorman <kogor...@gmail.com> >> wrote: >> > I just ran "emerge -p --depclean" and the only thing it wants to remove >> > is >> > gentoo-sources-2.6.35-r12. So my system's pretty clean, but I'm quite >> > puzzled with this result. >> > >> > I have 5 versions of gentoo-sources installed, and the one it wants to >> > ditch >> > is the one I'm actually using. I can understand why it wouldn't care >> > about >> > that, but why not: >> > 2.6.31-r10 which is no longer in the tree >> > any of the others, which are marked in exactly the same way as the >> > victim it picked? Some are older, and some are newer than this >> > victim. What gives? >> > >> > I'm just wondering about how --depclean picked on this one of the five? >> >> >> Look in /var/lib/portage/world and see if you are protecting the >> versions you think it should be cleaning but it isn't. >> >> Hope this helps, >> Mark >> > I looked there, and there's > sys-kernel/gentoo-sources > so I would expect them all to be protected. Why the exception? > ++ kevin >
No, that means only the latest one is protected. One of my machines has sys-kernel/gentoo-sources sys-kernel/gentoo-sources:2.6.33 which implies the latest is protected as well as 2.6.33. If I ran emerge -C gentoo-sources those two at least would be saved. If you specifically want to protect a kernel, maybe you require it for driver reasons or something, you can add a line like the above by hand or you can use the instructions on the screen when running emerge -p --depclean to add it. Hope this helps, Mark
