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