| 1 |
On 10/02/20 16:25, David M. Fellows wrote: |
| 2 |
>> On 2020-10-02 10:45, n952162 wrote: |
| 3 |
>>> Have I successfully updated my system? |
| 4 |
>>> |
| 5 |
>>> I ran this command: |
| 6 |
>>> |
| 7 |
>>> emerge \ |
| 8 |
>>> -v \ |
| 9 |
>>> --verbose-conflicts \ |
| 10 |
>>> --deep \ |
| 11 |
>>> -update \ |
| 12 |
>>> --changed-use \ |
| 13 |
>>> --keep-going \ |
| 14 |
>>> --with-bdeps=y \ |
| 15 |
>>> --changed-deps \ |
| 16 |
>>> --backtrack=100 \ |
| 17 |
>>> @world |
| 18 |
>>> |
| 19 |
>>> and got tons of stuff that looks like spurious debugging/tracing info |
| 20 |
> Probably not. And a good thing too. |
| 21 |
> Assuming the above is an accurate transcription of the command you used. |
| 22 |
> |
| 23 |
> -update is definitely NOT the same as --update. |
| 24 |
> |
| 25 |
> -update is equivalent to -u -p -d -a -t -e |
| 26 |
> so --update --pretend --debug --ask --tree --empty-tree |
| 27 |
> --debug, --tree produce voluminous output, |
| 28 |
> --empty-tree says rebuild everything. |
| 29 |
> |
| 30 |
> Hope this helps. |
| 31 |
> |
| 32 |
> DaveF |
| 33 |
> |
| 34 |
> |
| 35 |
|
| 36 |
Yes, now my emerge is failing again in the way I'd expected it to fail ;-) |
| 37 |
Thank you for debugging for me :-) |
Archives