[prev in list] [next in list] [prev in thread] [next in thread]
List: gentoo-project
Subject: Re: [gentoo-project] New developer: Matt "prometheanfire" Thode
From: Pandu Poluan <pandu () poluan ! info>
Date: 2011-11-11 6:18:59
Message-ID: CAA2qdGXTfmDpLJXiHfDYE=oy3mK9wyjc11Zm-wR3evXQqXpFCQ () mail ! gmail ! com
[Download RAW message or body]
On Nov 11, 2011 9:56 AM, "Jorge Manuel B. S. Vicetto" <
jmbsvicetto@gentoo.org> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Welcome aboard Matt.
>
> On 10-11-2011 05:28, Matt Thode wrote:
> > http://www.jmbsvicetto.name/ has them :P
> >
> > -- Matthew Thode
>
> > On Nov 9, 2011, at 7:24 PM, Pandu Poluan wrote:
> >
> >> Yay!
> >>
> >> Looking forward to up-to-date hardened stage3 tarballs for amd64
> >> ;-)
> >>
> >> Rgds,
>
> Pandu / others,
>
> so there's no confusion, the hardened team is not responsible for
> creating the stages (hardened or not).
> If there's anyone to "blame" for this, it's the release team and me in
> particular as the one responsible for the weekly builds for amd64 / x86.
> For anyone interested, this is assumed to be an issue with the release
> box doing the weekly stages[1]. That's why I've been creating new
> stages on my own hardware[2], using the official specs, and that we
> should be soon moving to a new box. The new box is similar to my own
> server, so there's no reason to believe the hardened stages will fail
> to build there.
>
> [1] - https://bugs.gentoo.org/show_bug.cgi?id=379777
> [2] - http://www.jmbsvicetto.name/releases/amd64/hardened/
>
Just not to be misunderstood, I'm not blaming anyone. In fact, I greatly am
respectful of Jorge's effort.
It *was* somewhat inconvenient to spend hours to upgrade
stage3-amd64-hardened to gcc-4.5.3, but I have learned my lesson, and now
maintain my own "stage3.1" tarballs.
I'm just thinking about people new to Gentoo who are looking for the above
stage3.
Anyways, thanks for the explanation, Jorge! Much appreciated :-)
Rgds,
[Attachment #3 (text/html)]
<p><br>
On Nov 11, 2011 9:56 AM, "Jorge Manuel B. S. Vicetto" <<a \
href="mailto:jmbsvicetto@gentoo.org">jmbsvicetto@gentoo.org</a>> wrote:<br> \
><br> > -----BEGIN PGP SIGNED MESSAGE-----<br>
> Hash: SHA1<br>
><br>
> Welcome aboard Matt.<br>
><br>
> On 10-11-2011 05:28, Matt Thode wrote:<br>
> > <a href="http://www.jmbsvicetto.name/">http://www.jmbsvicetto.name/</a> has \
them :P<br> > ><br>
> > -- Matthew Thode<br>
><br>
> > On Nov 9, 2011, at 7:24 PM, Pandu Poluan wrote:<br>
> ><br>
> >> Yay!<br>
> >><br>
> >> Looking forward to up-to-date hardened stage3 tarballs for amd64<br>
> >> ;-)<br>
> >><br>
> >> Rgds,<br>
><br>
> Pandu / others,<br>
><br>
> so there's no confusion, the hardened team is not responsible for<br>
> creating the stages (hardened or not).<br>
> If there's anyone to "blame" for this, it's the release team \
and me in<br> > particular as the one responsible for the weekly builds for amd64 \
/ x86.<br> > For anyone interested, this is assumed to be an issue with the \
release<br> > box doing the weekly stages[1]. That's why I've been \
creating new<br> > stages on my own hardware[2], using the official specs, and \
that we<br> > should be soon moving to a new box. The new box is similar to my \
own<br> > server, so there's no reason to believe the hardened stages will \
fail<br> > to build there.<br>
><br>
> [1] - <a href="https://bugs.gentoo.org/show_bug.cgi?id=379777">https://bugs.gentoo.org/show_bug.cgi?id=379777</a><br>
> [2] - <a href="http://www.jmbsvicetto.name/releases/amd64/hardened/">http://www.jmbsvicetto.name/releases/amd64/hardened/</a><br>
></p>
<p>Just not to be misunderstood, I'm not blaming anyone. In fact, I greatly am \
respectful of Jorge's effort.</p> <p>It *was* somewhat inconvenient to spend \
hours to upgrade stage3-amd64-hardened to gcc-4.5.3, but I have learned my lesson, \
and now maintain my own "stage3.1" tarballs.</p> <p>I'm just thinking \
about people new to Gentoo who are looking for the above stage3.</p> <p>Anyways, \
thanks for the explanation, Jorge! Much appreciated :-) </p> <p>Rgds,<br>
</p>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic