1 |
On Nov 11, 2011 9:56 AM, "Jorge Manuel B. S. Vicetto" < |
2 |
jmbsvicetto@g.o> wrote: |
3 |
> |
4 |
> -----BEGIN PGP SIGNED MESSAGE----- |
5 |
> Hash: SHA1 |
6 |
> |
7 |
> Welcome aboard Matt. |
8 |
> |
9 |
> On 10-11-2011 05:28, Matt Thode wrote: |
10 |
> > http://www.jmbsvicetto.name/ has them :P |
11 |
> > |
12 |
> > -- Matthew Thode |
13 |
> |
14 |
> > On Nov 9, 2011, at 7:24 PM, Pandu Poluan wrote: |
15 |
> > |
16 |
> >> Yay! |
17 |
> >> |
18 |
> >> Looking forward to up-to-date hardened stage3 tarballs for amd64 |
19 |
> >> ;-) |
20 |
> >> |
21 |
> >> Rgds, |
22 |
> |
23 |
> Pandu / others, |
24 |
> |
25 |
> so there's no confusion, the hardened team is not responsible for |
26 |
> creating the stages (hardened or not). |
27 |
> If there's anyone to "blame" for this, it's the release team and me in |
28 |
> particular as the one responsible for the weekly builds for amd64 / x86. |
29 |
> For anyone interested, this is assumed to be an issue with the release |
30 |
> box doing the weekly stages[1]. That's why I've been creating new |
31 |
> stages on my own hardware[2], using the official specs, and that we |
32 |
> should be soon moving to a new box. The new box is similar to my own |
33 |
> server, so there's no reason to believe the hardened stages will fail |
34 |
> to build there. |
35 |
> |
36 |
> [1] - https://bugs.gentoo.org/show_bug.cgi?id=379777 |
37 |
> [2] - http://www.jmbsvicetto.name/releases/amd64/hardened/ |
38 |
> |
39 |
|
40 |
Just not to be misunderstood, I'm not blaming anyone. In fact, I greatly am |
41 |
respectful of Jorge's effort. |
42 |
|
43 |
It *was* somewhat inconvenient to spend hours to upgrade |
44 |
stage3-amd64-hardened to gcc-4.5.3, but I have learned my lesson, and now |
45 |
maintain my own "stage3.1" tarballs. |
46 |
|
47 |
I'm just thinking about people new to Gentoo who are looking for the above |
48 |
stage3. |
49 |
|
50 |
Anyways, thanks for the explanation, Jorge! Much appreciated :-) |
51 |
|
52 |
Rgds, |