Gentoo Archives: gentoo-catalyst

From: "Rick \\\"Zero_Chaos\\\" Farina" <zerochaos@g.o>
To: gentoo-catalyst@l.g.o
Subject: Re: [gentoo-catalyst] [PATCH 1/2] Fix update_seed use by not using nor building binary packages during the seed update.
Date: Tue, 28 May 2013 19:54:21
Message-Id: 51A50B89.2080506@gentoo.org
In Reply to: Re: [gentoo-catalyst] [PATCH 1/2] Fix update_seed use by not using nor building binary packages during the seed update. by Brian Dolbec
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA1
3
4 On 05/28/2013 03:33 PM, Brian Dolbec wrote:
5 > On Tue, 2013-05-28 at 14:50 -0400, Rick "Zero_Chaos" Farina wrote:
6 >> On 05/28/2013 01:59 PM, Brian Dolbec wrote:
7 >
8 >>> Existing gcc binpkgs have been linked to libmpc.so.2 and portage does
9 >>> not check that all lib links exist before qualifying the binpkg to be
10 >>> installed. Therefore installing a gcc binpkg is a hit and miss
11 >>> proposition. Making it's use un-reliable. Therefore until the
12 >>> toolchain is migrated to eapi 5 with proper subslot use. Using binpkgs
13 >>> is unreliable for update_seed.
14 >>
15 >> In fact, the command is "--rebuild-if-new-ver" not
16 >> "--reinstall-if-new-ver". As such, the original reporter of this bug
17 >> and I both seem to think that even with --usepkg, gcc should be rebuilt:
18 >>
19 >> https://bugs.gentoo.org/show_bug.cgi?id=461422
20 >>
21 >> That's obviously not how it is, but I feel we should focus our attention
22 >> on fixing this properly.
23 >>>
24 >
25 > I think you did a typo there. There are 2 portage options
26 > --rebuild-if-new-ver and --rebuild-if-new-rev. I opted for the *-ver
27 > (version), since most revisions would not need to trigger a rebuild.
28 > But the failure in that bug should be the same or similar fix to our
29 > needs.
30
31 Not sure how *I* did a typo, looks like I typed the command properly
32 above, and I've not even commented on the bug yet... Yeah I do realize
33 that the bug is talking about -rev not -ver but the affected code
34 appears to be shared hence why it's brought up.
35 >
36 >> As a rule, we don't want to hack around limitations in portage to make
37 >> catalyst work. The toolchain team seems to have made it very clear they
38 >> aren't updating to eapi5 soon, but the portage team has been fixing
39 >> things left and right based on little more than my whims, I'd give them
40 >> a chance to fix this before throwing hacks into catalyst to work around
41 >> limitations in the package manager.
42 >>
43 >> Thanks,
44 >> Zero
45 >>>
46 >
47 > If someone wants to work on fixing it. The solution will require
48 > extracting the NEEDED.ELF.2 info from the binpkg and confirming that the
49 > links exist. If any of them don't, then trigger the build from source.
50 > Rejecting the existing binpkg.
51 >
52 > You may also want to talk to blueness, he created a utility for looking
53 > for broken elf links.
54
55 Here is where I admit to being lazy, I was planning on "fixing" it by
56 just triggering the src build no matter what when a rebuild occurs and
57 then hoping that someday people in gentoo actually use EAPI5 and make
58 this all unnecessary.
59
60 - -Zero
61 >
62 >
63 >
64 >
65
66 -----BEGIN PGP SIGNATURE-----
67 Version: GnuPG v2.0.19 (GNU/Linux)
68 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
69
70 iQIcBAEBAgAGBQJRpQuJAAoJEKXdFCfdEflKtI8P/iNpLeHAKD6E8li0hm2Pw5RI
71 CM0HfvYmLioKdevAvlbvMjNiI/WgwgmOuF8Stj8biFZn80vYQpDYwuei6jEvnuSO
72 wTBNmnI+v6kC91rVb7LTdpIOXpfCg3V27kHRNOWqNnyVSd4WK6kKjp6c2YqHcnwl
73 2bxHFjvOXFK8s/n9PVrBBgn5VrMqQzlc4VqVPn5FHQJP2/aMBpVChwrAZBcS6nGI
74 8wMVYMMfjwypk8jdroSTQC32Etw/T1jwcWPvUhgqtU7BCmGRSC1zXu22RuwfiLmK
75 WPd2BmMl2jqBo6FOPSx83JfN+/OKumJy55aiz7LMVF+STPIfsSuzvvcipDJV2inv
76 s8mkVXybpSYs/fdbpUEcx2fRuAeseSTAf96iMVVpjcKeFEavMxWzTSOwwQqFOkIy
77 m8Gy8zON0YbpNZA/Zy5FnChYJ0R7ci8s0keEeVozMqE82XfgyAlkJFW771XQUs26
78 T+bK8sDgpANRxPx4c8AT18+Sudkplo7u06kDsRkQ+Ru2Plc9lsVYkpbI1FjjwG7X
79 uxCjiigCZA5Y+x4tnoDo6Rl8rAhllRTuHbzZpjbvZXxFlYHgrMsSQzPNgwW7UqgC
80 iIIYCd6rVrfSsc2qtgedJacdMYHTTGGy+Hq1SWNHWqsedhd063q4HJ3Wqk6Epivu
81 nAtvVC7SFo/f++WU36+z
82 =2knI
83 -----END PGP SIGNATURE-----