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 6A53E1381F3 for ; Thu, 11 Apr 2013 18:53:55 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D428DE0B07; Thu, 11 Apr 2013 18:53:49 +0000 (UTC) Received: from vms173001pub.verizon.net (vms173001pub.verizon.net [206.46.173.1]) by pigeon.gentoo.org (Postfix) with ESMTP id 58AB4E0B07 for ; Thu, 11 Apr 2013 18:53:49 +0000 (UTC) Received: from odin.tremily.us ([unknown] [72.68.100.81]) by vms173001.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0ML300A8XTTOXN40@vms173001.mailsrvcs.net> for gentoo-catalyst@lists.gentoo.org; Thu, 11 Apr 2013 13:53:48 -0500 (CDT) Received: by odin.tremily.us (Postfix, from userid 1000) id D366995D5DF; Thu, 11 Apr 2013 14:53:47 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tremily.us; s=odin; t=1365706427; bh=vqGhXcReofp5vB+nhNJq78g0gr69CHWPo1kGndCUNy4=; h=Date:From:To:Subject:References:In-Reply-To; b=UJ23/LJAL1qPAjEGibmIBDMNGaY0yV9gmtzNa20a2CC1SH02WSfTnBPa3O4B43ndb 7F7BaDYQKK2HZ8XuT8ClwvBTzWkoTuIIIcgYIZBQ5Ly5iH9kAZgCZq6XgyZ/bijAFY GyYMDyUD9mxp7EHTLWa8+9dVe7EKGDxOiliKHXXc= Date: Thu, 11 Apr 2013 14:53:47 -0400 From: "W. Trevor King" To: gentoo-catalyst@lists.gentoo.org Subject: Re: [gentoo-catalyst] Binary package dependencies and update_seed Message-id: <20130411185347.GA15002@odin.tremily.us> References: <513A2F19.5040203@gentoo.org> <6472ad55830b40f838356a1b083b3815a4112358.1362768301.git.wking@tremily.us> <20130309121023.GE26574@odin.tremily.us> <20130411170941.GA14224@odin.tremily.us> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-catalyst@lists.gentoo.org Reply-to: gentoo-catalyst@lists.gentoo.org MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary=FL5UXtIhxfXey3p5 Content-disposition: inline In-reply-to: OpenPGP: id=39A2F3FA2AB17E5D8764F388FC29BDCDF15F5BE8; url=http://tremily.us/pubkey.txt User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: 360b6078-6dcc-47d1-8def-e74c76d8ed46 X-Archives-Hash: ffa2b10a1afc5dccfd075889f707a2c5 --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 11, 2013 at 11:22:54AM -0700, Matt Turner wrote: > On Thu, Apr 11, 2013 at 10:09 AM, W. Trevor King wrote: > > In order to avoid problems like this, it's probably a > > good idea to remove all the cached stuff with something like [1]: > > > > $ rm -rf --one-file-system /var/tmp/catalyst/{kerncache,packages,tmp} > > > > before building your stage1. >=20 > Not sure this is the way to go. I'll have to think through the > implications. Consider your stage1 build dies with some stupid tree > breakage that you can fix in your portage snapshot and restart the > stage build. This is going to cause your stage to rebuild everything. There shouldn't be a need to clear the caches unless you've changed the specs or sources. Presumably you had to change something to fix whatever killed stage1. If that was an ebuild problem, it's unlikely that your fix changed an ABI without also changing the package version and you should be ok keeping the old binary packages. > Wouldn't disabling the use of binary packages during the seed stage > update fix this? Disabling creation of binary packages during the seed stage update would help, and disabling the use of binary packages during the stage1 build would help. However, what if you have built a binary package for GCC and then you update your tree to something that builds libmpc.so.3. In this case, you're in trouble if you use your old GCC binary packages anywhere based on the new tree. Cheers, Trevor --=20 This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy --FL5UXtIhxfXey3p5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJRZwa5AAoJEEUbTsx0l5OMjJ4P/19kw0stXvO3OlmFWxyUDUOU wAdhXDzzc7AbE1C4tiE/ZP9wkFVUC5AstLyGcSQqqTIxrAm+OR289NU4UZUZ7znC c6cIyYlro+ABP4sNo+Wq7iOD+1ix8PBA+B5Bbg+cMmyTr2QFEw9zZJBCMvVeTjre 1Sp7ZrdMIRBfodc+Gx2i6a7EDmoK62mNHFJ6u82bcnbIXnUw91Yz9+ros0Y2ppDp R2ah5QfkaWNfXUHqMfmaP3QTOTK9Qlz/W0A+StOusiJ841bzN7E58LWDc5ISMGvH J9qC8hSEI1/vnHXRJ3OuMGejGUNaAw/iMsihvSvfKWGjSfeW9UF+QjJk3UD39sV1 Kk535UdnJKvBDvvitx5QP12GjTtRNVEbwvc8V4Huxf29hzUSp3VOixg2c568ngki CRvPT+j6CDe+YpyhZ0l56OzJaAnHo+b0yLsFF2k7epDVqIhl5A5Renk0+jt0izBZ nymegkKcCGiFQulmmlUOgAWsAm9xLHkBaz9pkebavT1oWZzlWvhyjLMR+NkhQvYM ySM4oT4u/+lGbOH7MTj4Ysn572RTJvId89F9lsWKW97Cr7dicFsxnUciZbJV+QBE rVPMr27R6cik2gPgCCDep1IkMaBT6FHucb/DdgiuHnCu8njSOOoGGny5QVuZyVgR BuSrw9Wh684fzxVLl+Z8 =gZp4 -----END PGP SIGNATURE----- --FL5UXtIhxfXey3p5--