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 467D01382C5 for ; Sun, 16 May 2021 12:24:37 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7DCE8E0866; Sun, 16 May 2021 12:24:31 +0000 (UTC) Received: from mout.web.de (mout.web.de [212.227.17.12]) (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 D36C5E0849 for ; Sun, 16 May 2021 12:24:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=dbaedf251592; t=1621167858; bh=KZK0xoGfqdzLbdWgHHhe/TH3eb4AGEHuW0g3q67qD1k=; h=X-UI-Sender-Class:Date:From:To:Subject:In-Reply-To:References; b=YOjsXzxYmireJdORdb3VAh6/wvaxCo766p3DuJctcRwwUtlouSqHiOCgh6LJZHZAN 1HJEhbojoVh/0lQNi5Y+oXzRquCPSanDXnx2h+5tTMIm8WT8/7U5tXAPVa+neeYnRx khOJfcKFFa7KJdZ7YJo1w/43DP1amhQXnAuBO4ss= X-UI-Sender-Class: c548c8c5-30a9-4db5-a2e7-cb6cb037b8f9 Received: from anfink-laptop ([213.55.224.128]) by smtp.web.de (mrweb103 [213.165.67.124]) with ESMTPSA (Nemesis) id 0Mgwhg-1m4L2I1VzM-00M3eI for ; Sun, 16 May 2021 14:24:18 +0200 Date: Sun, 16 May 2021 14:24:10 +0200 From: Andreas Fink To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] What does emerge status R mean? Message-ID: <20210516142410.3f490ee6@anfink-laptop> In-Reply-To: <56658d89-95cc-5d24-432a-8484ec8ec19a@web.de> References: <75dc51cf-4a06-25d4-d851-6c5dedc69887@web.de> <5038fff1-9585-b4c4-6349-a1f40e007a13@web.de> <20210516102330.6718dbdc@digimed.co.uk> <1f069789-a82f-f9da-45fd-a91b3746395c@web.de> <20210516102808.5849044a@digimed.co.uk> <20210516125322.230b4838@anfink-laptop> <56658d89-95cc-5d24-432a-8484ec8ec19a@web.de> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) 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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:DAr0+yJeg9A9g1lIDzKlZYSfBZuPJ1fxN9pzHnH1OvqzvbYG6fI kuFmBEMITy1K/OGk6YpiHZ3ePO/cApyxupf44cz6TGQGl6oYwS5G2KxuuugMadkXJht2iT4 +l8pSTWzOY028SFft8rioKmHway8KA8KfNUAwvwAkNwOZw/rdY0zhxYLHcanjqwPRM74msG iaA1MbgneXrSc7DI7HLbQ== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:GwdBrLI0oXI=:k8DQOYjLXpFqcaRCqzV2KL rExF3Y2fvzV9HCf4NeOf0CyZ4cBJn6j1GzsjPRfKnn5XH7t3svQ52smk0t8YA2MhRfSFCh/eR AIWr/xmBsbeV8ImsCXqiONixnIIVTrmzUJLlF7PEO+tvA2JMjKG240DqlmuPw8WvnGanilZfc 1thq6mXJfa3zS2F+nHKBT1xyejZET38eq2cZjqPbepjn2PEbrbEBCwBwOuANmZURTMo2GUGiX TFujyCMtEbryEdkJaZGU5BnQVn30TyiBLIl2m/ueLaEejEIuR5uWBgIqH302igmnb7CqYG1bD dpZ4YGeKrl2GhwANfX+Mq19RIYpKpe3vJQzaxerEmCuu5MbTaBOLa7J0VfwS8O4mvC2FAhLlT qWmZKzvlnz8e/xj5nfrG3ODu2X6z8v5t1UZz6qD94lJmMzTaUhKs+egllRdtO+tDFm0ofTYPL Tu0WKMc0NDL+DFZgxSS7JoAcaOa6onmoOT55waK5uF40LVDiCouEgH3M99akqH2dxEpB9aqUo r3fvN+iJuDEwuArzOeKH5MFzmfzl0t6zF+rmMs3xLkZg6lU6UJfbmIqvR51jiE489+Yt9D+Q6 tmT/3+0YPr7Lal7i3ENYX/2S/Dwbv/k8DEyx6EaiUvhAEfFbXcSIJXHnDc0OueA78LJj66VVu rVvsPSsEBO34Z/kijG4FannuXBV6yznRJvnaJs1KYHiXr72/WVTBpzfrEeUEtIA+SAtkYmYwB lg4JRISsb4EIBNrhdduHFGtqCmeotHsNq+9RpJfzP4vXwkrOD5VYNXmzsbvj60fmHAYXM0Q6M in54ppZ896AxDr09ml1Qa+0Dhww3Rx5zcKrNc5PBKrxZ52TQWvsVYJfeHNZvIq/kpSsV7AoQK Ru+b1IbaIW7rmt7Ebt9zQZ398IbeNrXDxml6JxuVFmZ50xeCDA4zqzN9scqukH/WP4U3Najz/ sOsVySijBI5LyyMKRTA0epDsA+iS9eL0FFkqkS0Rd8rLFoxL7rrFOp1jFg6Wb8xAcAjq59Zr9 BtL7iwFp8CkNu2XqDpKFNPk78i3w5DxUrBT7Q4akQVEgTvlkq99rs7N+25R0ymBKcFz8SL5xN kVYjqm1CQGC8iJIqK+UO3ziXDJVDR/qNGtHIqIEuHim6XxaK+aGdZ4MTXSO06r1SlHT5MGjL0 ROdaExdsXXuGOkyUGDsLHsjf2F7K04dh/Y01LTIBFCerS85wEw2y02lc11o16iBxX+4FI= X-Archives-Salt: 386ac70f-15a2-426e-be1a-912de839b242 X-Archives-Hash: c016c30a73adf009ea07a0c902271fd9 On Sun, 16 May 2021 13:14:26 +0200 n952162 wrote: > On 5/16/21 12:53 PM, Andreas Fink wrote: > > On Sun, 16 May 2021 12:49:26 +0200 > > n952162 wrote: > > =20 > >> On 5/16/21 11:28 AM, Neil Bothwick wrote: =20 > >>> On Sun, 16 May 2021 11:26:37 +0200, n952162 wrote: > >>> =20 > >>>>>> There are no use flags defined for any of the packages I did a ran= dom > >>>>>> check for, either on the server or the client.=C2=A0 I am worried = that it > >>>>>> is as you say: that the ebuild has a change of USE flags, which, of > >>>>>> course, has nothing to do with me, the user. =20 > >>>>> As already stated, any USE flag changes would appear in the emerge > >>>>> output, this is most likely caused by --changed-deps. Try with > >>>>> --changed-use but without --changed-deps to see. > >>>>> > >>>>> =20 > >>>> I have introduced that into my build script.=C2=A0 But, if it's as y= ou say, > >>>> the one is a subset of the other, it should have no effect on the > >>>> output, right? > >>>> =20 > >>> --changed-use is a subset of --newuse. --changed-deps is separate. > >>> > >>> =20 > >> Ah, I oversaw that. > >> > >> Ah. why would I want to have --changed-deps anyway?=C2=A0 That suddenl= y seems > >> silly. > >> > >> It's unfortunate, if there's no explanatory display if a package got > >> disqualified for that reason. > >> > >> =20 >=20 > Trying to comprehend here... >=20 > > If you want to have a binhost, then --changed-deps will become > > "necessary" at some point. Let me draw you a picture, where a binhost > > would fail to provide the correct package: > > - Binhost builds on day 1 package XYZ(i.e. server updates from intern= et) > > - computer that would merge with packages from binhost is NOT updated= (client does NO emerge on that day) > > - the dependencies are changed on day 2(i.e. XYZ is emerged onto serv= er, with changed dependencies in the ebuild) > > - Binhost does NOT rebuild, because you do not have --changed-deps > > enabled on day 2*(what is "Binhost" here? The --changed-deps is spe= cified on the client)* > > - Computer that merges from the binhost is updated on day 2 but will > > NOT use the binary package from binhost, because the dependencies do > > not match > > There are flags to ignore dependency mismatches, but the default would > > just not use the binary package. > > > > Cheers > > Andreas > > =20 > What does changed-deps mean, actually? >=20 > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 --changed-deps [ y | n ] > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 Tells=C2=A0 emerge=C2=A0 to=C2=A0 replace=C2=A0 installed=C2=A0 pack= ages for which > the corresponding > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 ebuild dependencies have changed since the packages were > built. ... >=20 > I presume it means that a package needed XYZ before, but now needs > XYZZ.=C2=A0 If I don't specify --changed-deps, that I might get a run-time > resolution problem. Changed dependencies means any change in the *.ebuild file with respect to the variables DEPEND/BDEPEND/RDEPEND/PDEPEND, e.g. version of a dependent package has changed, new package was added as dependency, a package was removed as dependency. All are dependency changes. If the changed *.ebuild file is commited to the portage tree WITHOUT a version-bump/revision-bump, then emerge would NOT rebuild the package, unless --changed-deps is given as an argument. >=20 > Or, does it mean that the package specified XYZ.1 in an excess of > precision and the new version specifies XYZ.3? >=20 > I just ran into this: >=20 > --binpkg-changed-deps [ y | n ] > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 Tells=C2=A0 emerge=C2=A0 to=C2=A0 ignore binary packages for which t= he > corresponding ebuild > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 dependencies have changed since the packages were built.=C2=A0 > In order=C2=A0 to=C2=A0 help > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 avoid=C2=A0 issues with resolving inconsistent dependencies, > this option is auto- > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 matically enabled unless the --usepkgonly option is > enabled.=C2=A0 Behavior=C2=A0 with > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 respect to changed build-time dependencies is controlled > by the --with-bdeps > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0 option. >=20 > But I haven't figured out what it means yet.=C2=A0 In particular, what all > the stated implications mean. >=20 This would be the option to ignore dependency mismatches of what the binary package claims its dependencies are (which you could see in $PKGDIR/Packages), and what the resolved dependencies are according to the *.ebuild file as portage is seeing it right now. Cheers Andreas