| 1 |
On 23/08/18 11:25, Adam Carter wrote: |
| 2 |
> The machine is actually a server, which just sat in a corner doing its |
| 3 |
> job perfectly. That's one of the reasons it wasn't updated: if it ain't |
| 4 |
> broken, don't fix it. |
| 5 |
> |
| 6 |
> |
| 7 |
> Any system that is not getting software updates is broken to some |
| 8 |
> degree, just in a subtle way. |
| 9 |
> |
| 10 |
> Trimming your /var/lib/portage/world file and removing the trimmed |
| 11 |
> packages can make the update less painful. I sometimes remove non-system |
| 12 |
> packages I want, then reinstall again later to get through difficult |
| 13 |
> upgrades. |
| 14 |
|
| 15 |
Bit late to the party, but yes this is normally my approach. |
| 16 |
|
| 17 |
If emerge lists a bunch of packages it thinks it can build, I explicitly |
| 18 |
just update them (on several occasions that has "miraculously" cleared |
| 19 |
the conflicts and the next global emerge just roars away). |
| 20 |
|
| 21 |
I wish there was a portage option that said "don't give up, just emerge |
| 22 |
what you can". |
| 23 |
|
| 24 |
If there are conflicts on something that doesn't appear crucial to the |
| 25 |
system, I just "emerge -C" it, and make a note to put it back later. |
| 26 |
|
| 27 |
My current home system is like this one, well out of date, but I'm |
| 28 |
planning to replace not fix it, because it's a multi-user system and |
| 29 |
*relies* on kdm which has, iirc, been deprecated and is not in kde5. |
| 30 |
Upgrading that is a task I do NOT fancy ... :-) |
| 31 |
|
| 32 |
Cheers, |
| 33 |
Wol |
Archives