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 DCDC71381F3 for ; Tue, 28 May 2013 19:54:21 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 62A47E0953; Tue, 28 May 2013 19:54:21 +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 CCBAAE0953 for ; Tue, 28 May 2013 19:54:20 +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 D931133DD01 for ; Tue, 28 May 2013 19:54:19 +0000 (UTC) Message-ID: <51A50B89.2080506@gentoo.org> Date: Tue, 28 May 2013 15:54:49 -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> <51A433BE.5040802@gentoo.org> <1369759349.3446.44.camel@big_daddy.dol-sen.ca> <51A4E0C3.3040104@gentoo.org> <1369763980.3446.71.camel@big_daddy.dol-sen.ca> <51A4FC90.8000005@gentoo.org> <1369769617.3446.83.camel@big_daddy.dol-sen.ca> In-Reply-To: <1369769617.3446.83.camel@big_daddy.dol-sen.ca> X-Enigmail-Version: 1.6a1pre Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 72332f32-fb0c-4994-ad38-2a3860cac9fb X-Archives-Hash: 97045eb1154b33683e88f0d51bfa1031 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/28/2013 03:33 PM, Brian Dolbec wrote: > On Tue, 2013-05-28 at 14:50 -0400, Rick "Zero_Chaos" Farina wrote: >> On 05/28/2013 01:59 PM, Brian Dolbec wrote: > >>> Existing gcc binpkgs have been linked to libmpc.so.2 and portage does >>> not check that all lib links exist before qualifying the binpkg to be >>> installed. Therefore installing a gcc binpkg is a hit and miss >>> proposition. Making it's use un-reliable. Therefore until the >>> toolchain is migrated to eapi 5 with proper subslot use. Using binpkgs >>> is unreliable for update_seed. >> >> In fact, the command is "--rebuild-if-new-ver" not >> "--reinstall-if-new-ver". As such, the original reporter of this bug >> and I both seem to think that even with --usepkg, gcc should be rebuilt: >> >> https://bugs.gentoo.org/show_bug.cgi?id=461422 >> >> That's obviously not how it is, but I feel we should focus our attention >> on fixing this properly. >>> > > I think you did a typo there. There are 2 portage options > --rebuild-if-new-ver and --rebuild-if-new-rev. I opted for the *-ver > (version), since most revisions would not need to trigger a rebuild. > But the failure in that bug should be the same or similar fix to our > needs. Not sure how *I* did a typo, looks like I typed the command properly above, and I've not even commented on the bug yet... Yeah I do realize that the bug is talking about -rev not -ver but the affected code appears to be shared hence why it's brought up. > >> As a rule, we don't want to hack around limitations in portage to make >> catalyst work. The toolchain team seems to have made it very clear they >> aren't updating to eapi5 soon, but the portage team has been fixing >> things left and right based on little more than my whims, I'd give them >> a chance to fix this before throwing hacks into catalyst to work around >> limitations in the package manager. >> >> Thanks, >> Zero >>> > > If someone wants to work on fixing it. The solution will require > extracting the NEEDED.ELF.2 info from the binpkg and confirming that the > links exist. If any of them don't, then trigger the build from source. > Rejecting the existing binpkg. > > You may also want to talk to blueness, he created a utility for looking > for broken elf links. Here is where I admit to being lazy, I was planning on "fixing" it by just triggering the src build no matter what when a rebuild occurs and then hoping that someday people in gentoo actually use EAPI5 and make this all unnecessary. - -Zero > > > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRpQuJAAoJEKXdFCfdEflKtI8P/iNpLeHAKD6E8li0hm2Pw5RI CM0HfvYmLioKdevAvlbvMjNiI/WgwgmOuF8Stj8biFZn80vYQpDYwuei6jEvnuSO wTBNmnI+v6kC91rVb7LTdpIOXpfCg3V27kHRNOWqNnyVSd4WK6kKjp6c2YqHcnwl 2bxHFjvOXFK8s/n9PVrBBgn5VrMqQzlc4VqVPn5FHQJP2/aMBpVChwrAZBcS6nGI 8wMVYMMfjwypk8jdroSTQC32Etw/T1jwcWPvUhgqtU7BCmGRSC1zXu22RuwfiLmK WPd2BmMl2jqBo6FOPSx83JfN+/OKumJy55aiz7LMVF+STPIfsSuzvvcipDJV2inv s8mkVXybpSYs/fdbpUEcx2fRuAeseSTAf96iMVVpjcKeFEavMxWzTSOwwQqFOkIy m8Gy8zON0YbpNZA/Zy5FnChYJ0R7ci8s0keEeVozMqE82XfgyAlkJFW771XQUs26 T+bK8sDgpANRxPx4c8AT18+Sudkplo7u06kDsRkQ+Ru2Plc9lsVYkpbI1FjjwG7X uxCjiigCZA5Y+x4tnoDo6Rl8rAhllRTuHbzZpjbvZXxFlYHgrMsSQzPNgwW7UqgC iIIYCd6rVrfSsc2qtgedJacdMYHTTGGy+Hq1SWNHWqsedhd063q4HJ3Wqk6Epivu nAtvVC7SFo/f++WU36+z =2knI -----END PGP SIGNATURE-----