On Wednesday 20 October 2004 07:14, Duncan wrote:
> The problem concisely is this:  Certain binary packages say they are
> corrupt and refuse to install, altho the tbz2 seems to be fine as does
> the ebuild tacked onto the end.  It's whatever other data is there that
> portage seems to be calling corrupt.
>
> Trigger situation setup is this:  I have hardware stability issues
> apparently related to SMP on my dual Opteron (so amd64).  Thus, with
> "long" ebuilds, such as gcc, glibc, xorg, and the kde ebuilds, I often
> find myself rebooting in the middle of the emerge.  No problem other
> than the frustration, normally, as I simply use ebuild to resume the
> compile or install steps (where it usually happens, not surprisingly)
> and continue from there as necessary.  Sometimes I go into the builddir
> and issue make there, then when it succeeds, I go back and do the
> ebuild and it redoes configure then (with most packages) zooms thru the
> compile since it's all done and continues.

It seems that this is the actual problem

I allways use packages, also when using ebuild for example for developing 
ebuilds (also bailing out halfway, but because of errors). I've never 
seen this behaviour. The only invalid packages I encountered anytime 
where created using quickpkg instead of with ebuild package.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@g.o
Homepage: http://www.devrieze.net