I am having some crazy issues with portage...just recently I emerged gaim0.67 which was an upgrade to my 0.65-r1. The ebuilding went on fine .. till I realized at the end that portage had installed the 0.67...and then removed the 0.65 as well as the new 0.67...it did this repeatedly...The only way I could get around it was by aborting teh emerge at the point where u have that count-down before unmerging takes place.
The same thing just happened as I tried to upgrade my vmware4.0.4460 to the 4.0.2.5592 build....it installed the new one and then at the end of the ebuild removed both of them....so I did the same thing...cancelled just before the unmerge event... I think my portage sub-system is seriously %^$%ed up any ideas how I can fix it....remember from a previous thread that it started when an upgrade to portage kept on removing itself and I had to do the emergency recover.
First, set AUTOCLEAN="no" in your /etc/make.conf before it does any more damage. That should keep Portage from trying to do the clean. Then try following the directions in /usr/portage/sys-apps/portage/files/README.RESCUE.
-- Andrew Gaffney
-- [EMAIL PROTECTED] mailing list
