Alan McKinnon wrote: > On 07/03/2017 21:46, Dale wrote: >> Helmut Jarausch wrote: >>> Hi, >>> I have packages which can't be updated at the moment, e.g. >>> dev-python/numba doesn't work with llvm-4.0.0(_rc3) >>> But this makes >>> >>> emerge -uvp --tree --unordered-display --verbose-conflicts --deep >>> --with-bdeps=y @world >>> >>> fail. Is there any means to proceed except masking all those packages >>> which can't be currently updated. >>> >>> Many thanks for a hint, >>> Helmut >>> >> Would --keepgoing work? Sometimes that doesn't work, depending on what >> packages depend on something that needs to be updated first. Also, >> sometimes --skipfirst comes in handy. > Helmut's question looks like emerge fails to make a list of stuff to > compile due to hard blocks. Not a compile failure. > > So --keep-going won't work >
I read it as a package fails, numba, and emerge stops. Either way, sometimes that option doesn't help anyway. Sometimes emerge has done all it can and it needs a human fix to carry on. Dale :-) :-)
