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 755041396D9 for ; Sat, 28 Oct 2017 17:58:42 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 866EF2BC10D; Sat, 28 Oct 2017 17:58:36 +0000 (UTC) Received: from auth-3.ukservers.net (auth-3.ukservers.net [217.10.138.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 291A1E0D12 for ; Sat, 28 Oct 2017 17:58:36 +0000 (UTC) Received: from [192.168.1.64] (host86-184-51-38.range86-184.btcentralplus.com [86.184.51.38]) by auth-3.ukservers.net (Postfix smtp) with ESMTPA id 65B765412F6 for ; Sat, 28 Oct 2017 18:58:33 +0100 (BST) Subject: Re: [gentoo-user] A portage nuisance To: gentoo-user@lists.gentoo.org References: <424ad9$4d4mm2@relay.skynet.be> <20171027145813.3a4fac70@peak.prhnet> <20171028175212.2fb3d76b5c3bcb8863fa00c7@gentoo.org> From: Wols Lists X-Enigmail-Draft-Status: N1010 Message-ID: <59F4C549.6010507@youngman.org.uk> Date: Sat, 28 Oct 2017 18:58:33 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 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 In-Reply-To: <20171028175212.2fb3d76b5c3bcb8863fa00c7@gentoo.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Archives-Salt: fec3f3d2-b076-4033-903a-375bc004fba9 X-Archives-Hash: 463ffbff34d0bd1f7e1bbcc1db561dbc On 28/10/17 15:52, Andrew Savchenko wrote: > On Fri, 27 Oct 2017 14:58:13 +0100 Peter Humphrey wrote: >> > On Fri, 27 Oct 2017 12:52:54 -0000 >> > Helmut Jarausch wrote: >> > >>> > > I have a problem with emerge for a long time. >>> > > Sometimes I need to (re-)emerge many packages like in an >>> > > emerge --emptytree @world >>> > > >>> > > Because I use several overlays, there are problems with a lot of >>> > > packages. >>> > > Unfortunately, emerge shows me just the first problem (like a missing >>> > > USE-flags) and then terminates. >>> > > Is there any means to let emerge go and report several (all) problems >>> > > which are independent of each other? >> > >> > EMERGE_DEFAULT_OPTS="--keep-going" ? > No, --keep-going allows to continue as long as possible after a > build failure. Helmut asks about dependecies resolution failures, > e.g. in some package REQUIRED_USE is not met, or circular > dependency occurs and so on. What I would like - a bit like --keep-going - is some option that tries again. When I do an "emerge -u" it sometimes blows up with this massive load of dependency failures. So what I end up doing is emerge a few packages that look like they're going to work, and then try my full update again. After several cycles through this, suddenly everything works. So my spec for what I would like is basically, as each package successfully resolves its dependencies, add it to a "try again" list. If the current list blows up in dependency hell, restart the emerge with just the packages in the "try again" list. When you haven't updated for a while and you've got a lot of packages, this "emerge what you can" approach certainly seems to work for me, it would just be nice if it was automated because it can take a lot of attempts (and time) before the system finally succeeds in updating itself. Cheers, Wol