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 669A213888F for ; Wed, 21 Oct 2015 19:26:23 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 98E23E080E; Wed, 21 Oct 2015 19:26:19 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1B730E080D for ; Wed, 21 Oct 2015 19:26:19 +0000 (UTC) Received: from [192.168.0.13] (ip174-67-193-3.oc.oc.cox.net [174.67.193.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id 3A6E834094F for ; Wed, 21 Oct 2015 19:26:17 +0000 (UTC) Subject: Re: [gentoo-portage-dev] [PATCH] emerge(1): document --oneshot caveats (bug 563482) To: gentoo-portage-dev@lists.gentoo.org References: <1445369394-24758-1-git-send-email-zmedico@gentoo.org> <562699BA.4010901@gentoo.org> <20151021003737.GA12188@fraenk> <56271E7C.60000@gentoo.org> <20151021161334.GA7917@fraenk> From: Zac Medico X-Enigmail-Draft-Status: N1110 Message-ID: <5627E6D3.1080603@gentoo.org> Date: Wed, 21 Oct 2015 12:26:11 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-portage-dev@lists.gentoo.org Reply-to: gentoo-portage-dev@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <20151021161334.GA7917@fraenk> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Archives-Salt: 9a5e290c-7399-4cda-a7f3-275e3e91e62f X-Archives-Hash: 1c0158d2b653e0fe5d8ff532cece3370 On 10/21/2015 09:13 AM, Rob Wortman wrote: > On 2015-10-20 at 22:11:24 -0700, zmedico@gentoo.org wrote: >> Any packages that are not reachable from @world are ripe for removal by >> --depclean, so we allow their dependencies to break in order to satisfy >> other dependencies (like in bug 563482). If you don't use --deep, then >> emerge may try to build something that depends on one of these >> unreachable packages with broken dependencies, such that whatever you >> are trying to build has broken indirect dependencies (which is likely to >> trigger a build failure like in bug 563482). > > I think I understand. So, one could get the hypothetical scenario: > > # emerge --oneshot A # which depends on B > # emerge --update @world # shuffles stuff around breaking B > # emerge C # which depends on A > > Package C's dependency is filled, so emerge goes ahead and builds C. > Now, either C fails to build, or it is installed but fails at runtime, > because it depends on a package which depends on a package which is > broken. > > Sound about right? > Yeah, and if you run emerge --depclean regularly, then it will prevent problems like these. -- Thanks, Zac