| 1 |
On Sun, Jun 7, 2020 at 5:07 PM Dale <rdalek1967@×××××.com> wrote: |
| 2 |
> |
| 3 |
> |
| 4 |
> Unless you have a really good reason to do so, you shouldn't try to update system by itself. It limits emerge and can lead to issues. |
| 5 |
|
| 6 |
He's just following my earlier advice. While what you say is true in |
| 7 |
general, the problem is that he is trying to update a system that |
| 8 |
hasn't been updated in ages, and so he probably needs to adjust dozens |
| 9 |
of USE flags/etc or make other tweaks to fix things. Using @system |
| 10 |
reduces the scope of the update to try to at least get the core system |
| 11 |
updated, but you're right that this might need to be augmented with |
| 12 |
other packages. |
| 13 |
|
| 14 |
Really though part of the problem here is that each time there is a |
| 15 |
problem I'm seeing about 10 lines of portage output, when I probably |
| 16 |
need 500 lines to figure out what is likely going on. Half the battle |
| 17 |
of the bug wranglers is getting people to just post all the stuff that |
| 18 |
the new bug form asks you to attach - we don't ask for thousands of |
| 19 |
lines of logs because we have nothing better to read... :) |
| 20 |
|
| 21 |
-- |
| 22 |
Rich |
Archives