Re: Bug#275620: netboot hang sparc32
- To: 275620@bugs.debian.org, debian-release@lists.debian.org
- Cc:
- Subject: Re: Bug#275620: netboot hang sparc32
- From: Blars Blarson <blarson@blars.org>
- Date: Sat, 9 Oct 2004 15:12:39 -0700
- Message-id: <[🔎] 200410092212.i99MCdCL018639@renig.nat.blars.org>
- In-reply-to: <20041009212245.GF4394@fsk.uni-heidelberg.de>
- References: <200410091909.i99J9JJb011488@renig.nat.blars.org> <20041009121927.GA4394@fsk.uni-heidelberg.de> <4163A3B20000B5FD@mail-6.tiscali.it> <200410090942.i999gb0W018638@renig.nat.blars.org> <20041009121927.GA4394@fsk.uni-heidelberg.de> <200410091909.i99J9JJb011488@renig.nat.blars.org>
In article <20041009212245.GF4394@fsk.uni-heidelberg.de>
>I was able to build rootskel 1.05 about two days ago on sparc using a
>sarge system. So rootskel is buildable in sarge, but not in sid.
Confirmed.
Release-managers: should I upload the version of rootskel I built on a
sarge system to sid? rootskel is currently holding up the build of
d-i rc2. (rootskel depends on glibc which does not build due to a
binutils bug.)
--
Blars Blarson blarson@blars.org
http://www.blars.org/blars.html
With Microsoft, failure is not an option. It is a standard feature.
Reply to: