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 252811381F3 for ; Tue, 28 May 2013 04:33:46 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 05777E07F0; Tue, 28 May 2013 04:33:41 +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 6EF02E07F0 for ; Tue, 28 May 2013 04:33:40 +0000 (UTC) Received: from [192.168.1.4] (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 52F86335E31 for ; Tue, 28 May 2013 04:33:39 +0000 (UTC) Message-ID: <51A433BE.5040802@gentoo.org> Date: Tue, 28 May 2013 00:34:06 -0400 From: "Rick \"Zero_Chaos\" Farina" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130524 Thunderbird/17.0.6 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] [PATCH 1/2] Fix update_seed use by not using nor building binary packages during the seed update. References: <1364353797-7607-1-git-send-email-jmbsvicetto@gentoo.org> In-Reply-To: <1364353797-7607-1-git-send-email-jmbsvicetto@gentoo.org> X-Enigmail-Version: 1.6a1pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: af1f8d29-6f8e-4b0b-a659-dc13a623255a X-Archives-Hash: 49fab45b7677123ccf00b628aaa946e7 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It has come to light that this patch breaks binpkg use in stage1. Personally I'd like to revert it entirely as the code is complex and confusing to me for no reason. Seperately I would fix the default update_seed command because the "--rebuild-if-new-ver gcc" bit seems a lot better to me. Everyone approved this patch and it's been sitting in git for 2 months without anyone realizing it's broken. That alone should make it evident that this code is too hard to read. Can I get an ACK or NACK from the team members? Thanks, Zero On 03/26/2013 11:09 PM, Jorge Manuel B. S. Vicetto (jmbsvicetto) wrote: > From: "Jorge Manuel B. S. Vicetto (jmbsvicetto)" > > --- > targets/stage1/stage1-chroot.sh | 5 ++++- > targets/support/chroot-functions.sh | 2 +- > 2 files changed, 5 insertions(+), 2 deletions(-) > > diff --git a/targets/stage1/stage1-chroot.sh b/targets/stage1/stage1-chroot.sh > index 3f628c2..ed83f38 100644 > --- a/targets/stage1/stage1-chroot.sh > +++ b/targets/stage1/stage1-chroot.sh > @@ -30,12 +30,15 @@ if [ -n "${clst_update_seed}" ]; then > if [ -n "${clst_update_seed_command}" ]; then > clst_root_path=/ run_merge "--buildpkg=n ${clst_update_seed_command}" > else > - clst_root_path=/ run_merge "--buildpkg=n --update --deep --newuse --onlydeps gcc" > + clst_root_path=/ run_merge "--update --deep --newuse --complete-graph --rebuild-if-new-ver gcc" > fi > elif [ "${clst_update_seed}" != "no" ]; then > echo "Invalid setting for update_seed: ${clst_update_seed}" > exit 1 > fi > + > + # reset emerge options for the target > + clst_update_seed=no setup_myemergeopts > else > echo "Skipping seed stage update..." > fi > diff --git a/targets/support/chroot-functions.sh b/targets/support/chroot-functions.sh > index 35ffbaa..0705b5b 100644 > --- a/targets/support/chroot-functions.sh > +++ b/targets/support/chroot-functions.sh > @@ -133,7 +133,7 @@ setup_myemergeopts(){ > then > export bootstrap_opts="${bootstrap_opts} -f" > export clst_myemergeopts="${clst_myemergeopts} -f" > - elif [ -n "${clst_PKGCACHE}" ] > + elif [ -n "${clst_PKGCACHE}" -a -z "${clst_update_seed}" ] > then > export clst_myemergeopts="${clst_myemergeopts} --usepkg --buildpkg --newuse" > export bootstrap_opts="${bootstrap_opts} -r" > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRpDO+AAoJEKXdFCfdEflKr2QP/0Whgw5sSD6MmcKYcFRm5f/F zJoKJ7bhGX5i2AOOFDj7C05ronjSPn5ADinEDNydBLLtrPkTSaMBvf+/XsJNRI8M 4IFAF39q3h4a7jBzRDI/SzjebXT1lJo2Tdx5HnF1lEJN28u8fyKoMW9SHRQXCqIt mOj8tt6Ajw8SFXGgDpkmwii9nvp3MP5vIsO/yKoMnZoUm6cLXN5kT9JiE8RpPyYy Gs7l4lVrBmwngGw40tpBNU5n1Koi3a7052qOQlUrdb4Bb29eVMEb53AbBGyvqZAb vyO/b52qLJn2LmLDmhyZsDxOl76i98OxzHTgd/b5yNcF3J3kv4gI1iWI7fQUO6YI gTpo5sZRzPvljAtqX3MfuLMtn5ZtsnxoKhSw1Oe30DBkcT0tzY36H/dNkdEA1WY0 Xh0i0UtwIgYKSU4WWMjsDErPtAbway2GuhfpSyjfGePaDiV84W3XvFQyBoBIQ6E8 g86t/y76mdINpqXKp7urYjb+o1CKt+zUQ+XoCOSkGDkA8yBhAheJu5RkLsztvvMd C1hz2u/HxDGxqaWw40fWTWI3RKywJbL/JMC+pWULqI9Wz4Fv6DkaUoVM0BToqkGP vgOVLbGc86t0mYYaSunUhZMQbSw99p0CdBUmxgnF8OyjPSJ9dd52ptiEFa3fllK/ vvGg8mlTjjWrmzliVBh4 =PNec -----END PGP SIGNATURE-----