From: Michael Orlitzky <michael@orlitzky.com>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] Hardened stage3 tarballs
Date: Tue, 07 Jun 2011 11:08:14 -0400 [thread overview]
Message-ID: <4DEE3EDE.8010307@orlitzky.com> (raw)
In-Reply-To: <20110606170518.305c043f@slaanesh.mthode.org>
On 06/06/11 17:05, Matthew Thode wrote:
> On Mon, 06 Jun 2011 16:38:06 -0400
> Michael Orlitzky <michael@orlitzky.com> wrote:
>
>> On 06/06/2011 03:54 PM, Sven Vermeulen wrote:
>>>
>>> The last one now is of 20110602, which is fairly recent.
>>>
>>> The autobuilds are not always created successfully. Updates on
>>> compilers or other toolchain changes might affect build successes.
>>> When these builds fail, they are not propagated so you'll have to
>>> "wait" a week (if you desperately need a build that's more recent
>>> than a few weeks old). Considering that Gentoo is a rolling upgrade
>>> distribution, working from a month-old stage is not an issue. Even
>>> several months old isn't an issue.
>>>
>>> Wkr,
>>> Sven Vermeulen
>>
>> That makes sense.
>>
>> What's the difference between autobuild/stage3-foo and
>> current-stage3/stage3-foo? I've always looked in current-stage3 in the
>> past (I think this is where the handbook taught me to look so long
>> ago).
>>
>
> I do not think there is a difference.
Well, I ask because the hardened stages are missing from the
current-stage3 directory but not autobuild.
next prev parent reply other threads:[~2011-06-07 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 16:08 [gentoo-hardened] Hardened stage3 tarballs Michael Orlitzky
2011-06-06 19:54 ` Sven Vermeulen
2011-06-06 20:38 ` Michael Orlitzky
2011-06-06 21:05 ` Matthew Thode
2011-06-07 15:08 ` Michael Orlitzky [this message]
2011-06-07 15:43 ` Francisco Blas Izquierdo Riera (klondike)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DEE3EDE.8010307@orlitzky.com \
--to=michael@orlitzky.com \
--cc=gentoo-hardened@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox