| 1 |
On Fri, Jan 05 2018, Daniel Frey wrote: |
| 2 |
|
| 3 |
> On 01/05/18 13:15, Neil Bothwick wrote: |
| 4 |
>> On Fri, 05 Jan 2018 13:00:20 -0500, allan gottlieb wrote: |
| 5 |
>> |
| 6 |
>>> I am finally moving my production machine the the 17.0 profile. |
| 7 |
>>> Currently running is |
| 8 |
>>> |
| 9 |
>>> emerge -e --keep-going @world |
| 10 |
>>> |
| 11 |
>>> So far there is one failure (libcryptui, the fix is easy). |
| 12 |
>>> |
| 13 |
>>> Am I correct that when the above emerge completes, I should run |
| 14 |
>>> simply |
| 15 |
>>> |
| 16 |
>>> emerge --resume |
| 17 |
>> |
| 18 |
>> If the emerge has completed, there is nothing to resume. Just make a note |
| 19 |
>> of the packages that failed to build ans emerge --oneshot them, with any |
| 20 |
>> necessary fixes. |
| 21 |
>> |
| 22 |
>> |
| 23 |
> |
| 24 |
> You may also want to check for dependencies (as in: `equery depends |
| 25 |
> <package>` and rebuild the dependencies of the failed package as well. |
| 26 |
> |
| 27 |
> Dan |
| 28 |
|
| 29 |
I don't understand. If the dependencies didn't fail, why should I |
| 30 |
rebuild them? |
| 31 |
|
| 32 |
thanks, |
| 33 |
allan |
Archives