| 1 |
On Saturday, 6 January 2018 02:49:53 GMT allan gottlieb wrote: |
| 2 |
> On Fri, Jan 05 2018, Neil Bothwick wrote: |
| 3 |
> > On Fri, 05 Jan 2018 13:00:20 -0500, allan gottlieb wrote: |
| 4 |
> >> I am finally moving my production machine the the 17.0 profile. |
| 5 |
> >> Currently running is |
| 6 |
> >> |
| 7 |
> >> emerge -e --keep-going @world |
| 8 |
> >> |
| 9 |
> >> So far there is one failure (libcryptui, the fix is easy). |
| 10 |
> >> |
| 11 |
> >> Am I correct that when the above emerge completes, I should run |
| 12 |
> >> simply |
| 13 |
> >> |
| 14 |
> >> emerge --resume |
| 15 |
> > |
| 16 |
> > If the emerge has completed, there is nothing to resume. Just make a |
| 17 |
> > note |
| 18 |
> > of the packages that failed to build ans emerge --oneshot them, with any |
| 19 |
> > necessary fixes. |
| 20 |
> |
| 21 |
> Thank you. So far (only 104 to go) just the one failure. Will the |
| 22 |
> emerge --keep-going |
| 23 |
> print a list of failed pkgs at the end? |
| 24 |
|
| 25 |
Yes, it will; it'll give you the same output from each failure as you would |
| 26 |
have got separately. |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
Regards, |
| 31 |
Peter. |
Archives