[gentoo-hardened] Hardened stage3 tarballs

[gentoo-hardened] Hardened stage3 tarballs

[Michael Orlitzky]

It looks like these stopped being published:

  http://distfiles.gentoo.org/releases/amd64/current-stage3/

Any reason? They can still be found here,

  http://gentoo.osuosl.org/releases/amd64/autobuilds/

but it looks like even those stopped being built a week ago.

Re: [gentoo-hardened] Hardened stage3 tarballs

[Sven Vermeulen]

[-- Attachment #1: Type: text/plain, Size: 875 bytes --]

On Fri, Jun 3, 2011 at 6:08 PM, Michael Orlitzky <michael@orlitzky.com>wrote:

> It looks like these stopped being published:
>
>  http://distfiles.gentoo.org/releases/amd64/current-stage3/
>
> Any reason? They can still be found here,
>
>  http://gentoo.osuosl.org/releases/amd64/autobuilds/
>
> but it looks like even those stopped being built a week ago.
>
>
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

[-- Attachment #2: Type: text/html, Size: 1378 bytes --]

Re: [gentoo-hardened] Hardened stage3 tarballs

[Michael Orlitzky]

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).

Re: [gentoo-hardened] Hardened stage3 tarballs

[Matthew Thode]

[-- Attachment #1: Type: text/plain, Size: 999 bytes --]

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [gentoo-hardened] Hardened stage3 tarballs

[Michael Orlitzky]

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.

Re: [gentoo-hardened] Hardened stage3 tarballs

[Francisco Blas Izquierdo Riera (klondike)]

[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]

El 07/06/11 17:08, Michael Orlitzky escribió:
> 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.
current-stage3 is a symlink to the last autobuild . If it failed it is
empty, as simple as that.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]