| 1 |
Helmut Jarausch wrote: |
| 2 |
> Hi, |
| 3 |
> this is nuissance all the time. |
| 4 |
> |
| 5 |
> Updating a machine which hasn't been updated for a long(er) time I try |
| 6 |
> |
| 7 |
> emerge -vup --changed-use --deep --tree --with-bdeps y @system @world |
| 8 |
> >/root/UPD |
| 9 |
> |
| 10 |
> But many times this stops prematurely with messages like |
| 11 |
> |
| 12 |
> emerge: there are no ebuilds to satisfy |
| 13 |
> ">=app-text/poppler-bindings-0.5.0" |
| 14 |
> |
| 15 |
> How can I keep emerge going and tell me these message all at once in |
| 16 |
> the end? |
| 17 |
> |
| 18 |
> Many thanks for hint, |
| 19 |
> Helmut. |
| 20 |
> |
| 21 |
> |
| 22 |
> |
| 23 |
|
| 24 |
|
| 25 |
This should help. From man emerge: |
| 26 |
|
| 27 |
--keep-going [ y | n ] |
| 28 |
Continue as much as possible after an error. When an error occurs, |
| 29 |
dependencies are recalculated for remaining packages and any with |
| 30 |
unsatisfied dependencies are automatically dropped. Also see the |
| 31 |
related --skipfirst option. |
| 32 |
|
| 33 |
You can also add that to make.conf if you want that all the time. There |
| 34 |
are times when emerge can't continue but if it can, it will. |
| 35 |
|
| 36 |
Dale |
| 37 |
|
| 38 |
:-) :-) |
| 39 |
|
| 40 |
-- |
| 41 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |
Archives