Re: release update: Etch 4.0, Blockers and Goals, Arch status, kernel 2.4, etc
On Mon, Jul 17, 2006 at 09:39:37PM +0100, Thiemo Seufer <ths@networkno.de> wrote:
> Mike Hommey wrote:
> > On Mon, Jul 17, 2006 at 10:06:19PM +0200, Bastian Blank <waldi@debian.org> wrote:
> > > On Mon, Jul 17, 2006 at 09:23:02PM +0200, Martin Michlmayr wrote:
> > > > It's not even RC at all, just a badly configured buildd. They should
> > > > be using linux32.
> > >
> > > No, it is configured correctly. The buildd provides a build environment
> > > which matches the standard configuration for this architecture.
> >
> > Except uname -m gives s390x instead of s390...
>
> It matches _a_ standard configuration, IOW, uname is an unreliable
> indicator.
Bastian said "_the_ standard configuration". Anyways, I'm not
responsible for upstream using uname... I'm trying to get a fix for the
issue but I have higher priority things I'd like to work on before
release... Thus I'm asking if that can be treated ignore-etch...
Mike
Reply to:
- References:
- Re: release update: Etch 4.0, Blockers and Goals, Arch status, kernel 2.4, etc
- From: Mike Hommey <mh@glandium.org>
- Re: release update: Etch 4.0, Blockers and Goals, Arch status, kernel 2.4, etc
- From: Martin Michlmayr <tbm@cyrius.com>
- Re: release update: Etch 4.0, Blockers and Goals, Arch status, kernel 2.4, etc
- From: Bastian Blank <waldi@debian.org>
- Re: release update: Etch 4.0, Blockers and Goals, Arch status, kernel 2.4, etc
- From: Mike Hommey <mh@glandium.org>
- Re: release update: Etch 4.0, Blockers and Goals, Arch status, kernel 2.4, etc
- From: Thiemo Seufer <ths@networkno.de>