From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.50) id 1EijNu-0001jA-D0 for garchives@archives.gentoo.org; Sun, 04 Dec 2005 02:13:50 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jB42D6YV028981; Sun, 4 Dec 2005 02:13:06 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jB42BIIC007784 for ; Sun, 4 Dec 2005 02:11:18 GMT Received: from zh032154.ppp.dion.ne.jp ([222.3.32.154] helo=opteron246.suzuki-stubbs.home) by smtp.gentoo.org with esmtpa (Exim 4.43) id 1EijLS-0007Vd-0w for gentoo-dev@lists.gentoo.org; Sun, 04 Dec 2005 02:11:18 +0000 Received: by opteron246.suzuki-stubbs.home (Postfix, from userid 1000) id A46D724917C; Sun, 4 Dec 2005 11:13:54 +0900 (JST) From: Jason Stubbs To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] emerge -e question Was: GCC-3.4 will be marked stable in ~1 hour on x86 Date: Sun, 4 Dec 2005 11:13:54 +0900 User-Agent: KMail/1.9 References: <20051202215523.GA25803@aerie.halcy0n.com> In-Reply-To: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512041113.54555.jstubbs@gentoo.org> X-Archives-Salt: 43f1d53e-cb28-48b2-9fa7-0bfabf5334e2 X-Archives-Hash: 37abee3e411257259413a6e326524407 On Saturday 03 December 2005 21:47, Duncan wrote: > Mark Loeser posted <20051202215523.GA25803@aerie.halcy0n.com>, excerpted > > below, on Fri, 02 Dec 2005 16:55:23 -0500: > > [1] http://www.gentoo.org/proj/en/base/x86/gcc-upgrading-guide.xml > > Reading this reminds me of a question I've had since I tried emerge -eav > world last time: > > When portage merges, it stops the emerge process, updates its metadata or > whatever, then restarts the process. With the -e in there, at least here, > it reissued the same command over again, thereby restarting the process > from the beginning and of course, upon getting to portage, looping yet > again! This is incorrect. Portage should only restart if the version that was merged does not match the internally recorded version. There was one or two releases that had an incorrect internal version but not for at least a year. However, if the version has changed and portage does restart itself then any packages listed before portage will be merged again. > Maybe it was because I was using -KuD also, to remerge/upgrade from binary > packages? (Hard disk trouble, I was remerging the binary packages to > bring up2date an old installation snapshot.) Perhaps you were using one of the broken versions? -- Jason Stubbs -- gentoo-dev@gentoo.org mailing list