From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 785AD138334 for ; Sat, 1 Sep 2018 09:39:31 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 963A6E0844; Sat, 1 Sep 2018 09:39:23 +0000 (UTC) Received: from smarthost03a.mail.zen.net.uk (smarthost03a.mail.zen.net.uk [212.23.1.20]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 27511E07F0 for ; Sat, 1 Sep 2018 09:39:22 +0000 (UTC) Received: from [82.69.80.10] (helo=peak.localnet) by smarthost03a.mail.zen.net.uk with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fw2NF-00018p-Au for gentoo-user@lists.gentoo.org; Sat, 01 Sep 2018 09:39:21 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Update circle Date: Sat, 01 Sep 2018 10:39:20 +0100 Message-ID: <7578919.uxL7V01PoZ@peak> In-Reply-To: <1f66bd7a-5dd2-3ad5-963f-1475173dd207@youngman.org.uk> References: <20180822182443.18693b55@linux-0ft9> <1f66bd7a-5dd2-3ad5-963f-1475173dd207@youngman.org.uk> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost03a-IP: [82.69.80.10] Feedback-ID: 82.69.80.10 X-Archives-Salt: 0e03a6e9-851a-4d49-a5df-7aaeb36c9dcd X-Archives-Hash: 246f84fa6451c2c87c2c2c6a880ab830 On Saturday, 1 September 2018 09:35:46 BST Wol's lists wrote: > On 23/08/18 11:25, Adam Carter wrote: > > The machine is actually a server, which just sat in a corner doing > > its > > job perfectly. That's one of the reasons it wasn't updated: if it > > ain't > > broken, don't fix it. > > > > Any system that is not getting software updates is broken to some > > degree, just in a subtle way. > > > > Trimming your /var/lib/portage/world file and removing the trimmed > > packages can make the update less painful. I sometimes remove non-system > > packages I want, then reinstall again later to get through difficult > > upgrades. > > Bit late to the party, but yes this is normally my approach. > > If emerge lists a bunch of packages it thinks it can build, I explicitly > just update them (on several occasions that has "miraculously" cleared > the conflicts and the next global emerge just roars away). > > I wish there was a portage option that said "don't give up, just emerge > what you can". There is: --keep-going > If there are conflicts on something that doesn't appear crucial to the > system, I just "emerge -C" it, and make a note to put it back later. > > My current home system is like this one, well out of date, but I'm > planning to replace not fix it, because it's a multi-user system and > *relies* on kdm which has, iirc, been deprecated and is not in kde5. > Upgrading that is a task I do NOT fancy ... :-) Yes, the recommended replacement is sddm, which I'm having problems with at the moment, as in the thread "KDE reboot not preserving running applications" -- Regards, Peter.