Johan Lindquist wrote:

> So anyway, it was like, 00:47 CEST Oct 22 2004, you know? Oh, and, yeah,
> Anno v. Heimburg was all like, "Dude,
>
>> Since the update to portage-2.0.51-r1, at the end an update, I get
>> "Unable to run required binary", e.g.:
>
> [..]
>
> I can't say anything about that, but for me 2.0.51 was horribly broken
> in that it didn't actually compile anything. It happily munched
> through the list of updates and recorded them as merged, but 'epm -ql'
> showed no files at all for a given package merged with 2.0.51, and an
> experimental 'ebuild <foo> compile' did nothing more than unpack the
> sources.
>
> In the end I followed the instructions in README.RESCUE and unpacked
> a 2.0.51-rc9 version of portage which I could then use to upgrade to
> 2.0.51-r2. This one seems to be working fine.
>
> Maybe that will work for you as well.
>
I found that I could install the packages that stopped short after issuing
emerge -u packagename. The ebuild resumed where it left off which is odd.

Needless to say I masked those versions of portage.
--
Stephen Fairchild