| 1 |
On 07/03/2017 21:46, Dale wrote: |
| 2 |
> Helmut Jarausch wrote: |
| 3 |
>> Hi, |
| 4 |
>> I have packages which can't be updated at the moment, e.g. |
| 5 |
>> dev-python/numba doesn't work with llvm-4.0.0(_rc3) |
| 6 |
>> But this makes |
| 7 |
>> |
| 8 |
>> emerge -uvp --tree --unordered-display --verbose-conflicts --deep |
| 9 |
>> --with-bdeps=y @world |
| 10 |
>> |
| 11 |
>> fail. Is there any means to proceed except masking all those packages |
| 12 |
>> which can't be currently updated. |
| 13 |
>> |
| 14 |
>> Many thanks for a hint, |
| 15 |
>> Helmut |
| 16 |
>> |
| 17 |
> |
| 18 |
> Would --keepgoing work? Sometimes that doesn't work, depending on what |
| 19 |
> packages depend on something that needs to be updated first. Also, |
| 20 |
> sometimes --skipfirst comes in handy. |
| 21 |
|
| 22 |
Helmut's question looks like emerge fails to make a list of stuff to |
| 23 |
compile due to hard blocks. Not a compile failure. |
| 24 |
|
| 25 |
So --keep-going won't work |
| 26 |
|
| 27 |
-- |
| 28 |
Alan McKinnon |
| 29 |
alan.mckinnon@×××××.com |
Archives