Today, i decided to clean my collection of old kernels. A few weeks ago, i tested the development-sources, release 2.6.1-rc1. And a few days later, the 2.6.1, etc... But today, when trying to remove 2.6.1-rc1, i saw that the ebuild for this version of the 2.6 kernel had disappeared. As a result : i couldn't manage to remove manually this specific version of this kernel. When trying to 'emerge unmerge development-sources-2.6.1-rc1', i got something like : no such package. But 'emerge unmerge development-sources-2.6.3' worked... Which could mean that portage needs the ebuild of a soft to be present in the tree in order to be able to remove it ? I finally found a 'clean' way to remove this version : 'emerge unmerge development-sources' removed all my 2.6 serie of kernels. And i emerged back the last one after. Hope i was clear, my english isn't perfect :(. Thanks !
i'm pretty sure a bug has already been filed for this but i cant seem to find it :/
Hey yes :) ! I searched for it too, but couldn't manage to find it nor :( . That's why i posted it !
emerge unmerge development-sources-2.6.1-rc1 * emerge unmerge development-sources-2.6.1_rc1 Is it just typo in this bug?
No, the problem was not a typo error. but i cannot reproduce the bug, since i solved it another way :( I will be hunting for this :) !
unmerge uses portdbapi, I'd imagine. The ebuild isn't searched for in the vardb, and it isn't used anyway (uses environment file). unmerge should check and discover info via vardbapi and check for an environment file.
CVS Head handles the issues above, beyond that this bus is basically a dupe of 56408 *** This bug has been marked as a duplicate of 56408 ***
