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 AFBA41381F3 for ; Thu, 11 Apr 2013 20:34:53 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3A19AE0AD3; Thu, 11 Apr 2013 20:34:53 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id AF26CE0AD3 for ; Thu, 11 Apr 2013 20:34:52 +0000 (UTC) Received: from [192.168.1.11] (pool-71-245-176-92.pitbpa.fios.verizon.net [71.245.176.92]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: zerochaos) by smtp.gentoo.org (Postfix) with ESMTPSA id A535733DC38 for ; Thu, 11 Apr 2013 20:34:51 +0000 (UTC) Message-ID: <51671EF3.5030902@gentoo.org> Date: Thu, 11 Apr 2013 16:37:07 -0400 From: "Rick \"Zero_Chaos\" Farina" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130406 Thunderbird/17.0.5 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 To: gentoo-catalyst@lists.gentoo.org Subject: Re: [gentoo-catalyst] Binary package dependencies and update_seed References: <513A2F19.5040203@gentoo.org> <6472ad55830b40f838356a1b083b3815a4112358.1362768301.git.wking@tremily.us> <20130309121023.GE26574@odin.tremily.us> <20130411170941.GA14224@odin.tremily.us> <516706A3.6000500@gentoo.org> <51670C69.1030801@gentoo.org> In-Reply-To: X-Enigmail-Version: 1.6a1pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: d0471758-131b-4f75-8730-ac781309ecc2 X-Archives-Hash: 06aae4f2cc33b29c46ca4b14fb7b7bd7 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/11/2013 04:24 PM, Matt Turner wrote: > On Thu, Apr 11, 2013 at 12:18 PM, Rick "Zero_Chaos" Farina > wrote: >> We already don't BUILD any new packages during update_seed. Originally >> we did, I encountered issues and fixed it in >> e7ea409acb52b43e9ea141c57201f9f87673f7ba to prevent building of packages >> during update_seed. > > Right, I see. > > So, to make sure that I'm on the same page: is the the problem that > we're using stale packages in stage1 and if so, where did they come > from? A previous stage1 build that didn't do update-seed? > > - From discussions in irc it sounds like he wasn't using update_seed at all originally. That means he encountered the bug which update_seed was meant to prevent (and built a bad binpkg at that time). Later he learned about update_seed, enabled it, and it didn't fix anything because the bad package was already built. Perhaps we should just force update_seed to on by default? - -ZC -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRZx7zAAoJEKXdFCfdEflK51gP/2yIxWpbgGDvlX5dle07jSGy g/kGZ+LudmLlRNcAExURpTxMMd5Jgm4WK8qU42BON2rgC+QmuD9opIPWefpYCiwN BzOvKejhB6cPUO5m5HABoSNUq0fqXtefMfCl9hEbzZfPaOKPz2vpVgzxWGz8uz2v IGukmkJ91SMUef673UHnk/EyIO6BQKeuTCzcKeZW8ym1r9Ut6w3PvKVqRRSVqSTr e0VHL5UKLN/4Z9/LBktbmTaNQeDLNuksIan0KORRAUGepBWmBVuUzmgekfDZoKqD 7n6Ig7RYLv8p+8i+XL7SI8PcYdxAP5WqmPnmXaDFhuhMmN8kjapomf/0rUoWeZiP DRausrPc7XIN+sDSWulkWhwB1buhLnwnZU2NTldvO1fi/P42oeCkpNGGiQnPtmBu x9x7fhmc0+M35VXBhzWPARxyl/JrAkB+xb9KoAC7uO6iLFb7m55Y6/SPpXuxlK8K 0mF+VfQXSRBIPnJWlzHZS83DKKQ6cHQT9oRLFdBPZJt/C8MMMY6hZPslytj7DX+F 6vNSv8wFBmMOzOvD98FIJ86TtFzbxrZMcFOYAY7I6DqeeJEK8hAT5pTs71l8W9+Y 3vMdvnTwlpIK5gmk3OubERQzCvve03gwRJn03XzSvBdIm41/fg+6gn5/pzLLeG/C ENqNf6fO0UUP0tphTNb1 =bD7X -----END PGP SIGNATURE-----