From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id ADBBF1384B4 for ; Sun, 15 Nov 2015 10:54:41 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3491521C18A; Sun, 15 Nov 2015 10:54:32 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1D57421C01C for ; Sun, 15 Nov 2015 10:54:31 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Zxux1-0004Cz-Hr for gentoo-user@lists.gentoo.org; Sun, 15 Nov 2015 11:54:27 +0100 Received: from 220-245-218-217.tpgi.com.au ([220.245.218.217]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 15 Nov 2015 11:54:27 +0100 Received: from linux by 220-245-218-217.tpgi.com.au with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 15 Nov 2015 11:54:27 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Hans Subject: [gentoo-user] Re: Emerge order not deterministic !? Date: Sun, 15 Nov 2015 20:52:43 +1000 Message-ID: References: <20151111193548.GB12926@waltdnes.org> <5644486F.1090205@gmail.com> <56444E0A.5030309@gmail.com> <20151112085430.7251a76a@digimed.co.uk> <20151112095102.619154f3@digimed.co.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-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 220-245-218-217.tpgi.com.au User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0 In-Reply-To: <20151112095102.619154f3@digimed.co.uk> X-Archives-Salt: 6860e65d-e7a2-407c-80cd-619fd18dcdd3 X-Archives-Hash: 74cf9a0b48fb23b3306e0bbf91a491a8 On 12/11/15 19:51, Neil Bothwick wrote: > On Thu, 12 Nov 2015 10:35:14 +0100, Jörg Schaible wrote: > >>> Then use emerge --keep-going and portage will take care of skipping >>> failing merges for you. >> >> Ah, no, that's not an option. It breaks for a reason. Sometimes I can >> ignore that and look for it later and in this case I skip it, but >> normally I fix the problem first. However, you have to take care, which >> package you're actually skipping. Especially if the build order is >> different with resume. > > --keep-going will emerge all unaffected packages, meaning you are then > working with a much smaller list when you try to fix the problem. At > least, that's the approach that normally works for me. > > --keep-going is intelligent enough to skip any packages that depend on > the failed package. That means you often end up with a package list that > is a single branch dependency tree, so the order is unlikely to change. > > I use the following commands to upgrade my Gentoo boxes: emerge --sync emerge --update --deep --with-bdeps=y --newuse --backtrack=300 --changed-deps=y --keep-going=y @world -va When necessary adding, deleting or changing use flags, keywords, masks. Followed by: emerge --depclean revdep-rebuild No more problems since using this sequence unless there is a bug in a ebuild, like the one last one in busybox ebuild.