-----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 > <[email protected]> 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-----
