On Wed, 22 Jun 2016 14:57:50 -0500, Dan Douglas wrote: > >> --keep-going is in EMERGE_DEFAULT_OPTS so the problem is only when > >> that fails for whatever reason, --resume (with or without > >> --skip-first) always fails too. > > On 06/22/2016 12:31 PM, Neil Bothwick wrote: > > That makes sense, --keep-going has already made sure that all updates > > that are not dependant on the failing one have emerged, so there's > > nothing left to emerge until you fix the broken package. > > > That's what it should do but it clearly doesn't quite work that way. > It's easy to prove it's broken by finding any package on the resume list > that can merge on its own without pulling in a previously failed > package. > > I've had completely up-to-date systems where no possible failure could > result in an unsatisfied dependency and portage refuses to resume an > `emerge -e @world` with hundreds of possible packages on the resume list > that would work in isolation. That's the problem.
Without specifics it's not possible to say any more. -- Neil Bothwick "There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult" -C.A.R. Hoare
pgpgBUMGRfNuJ.pgp
Description: OpenPGP digital signature
