On Tue, Aug 17, 2010 at 11:13:44PM +0200, Josip Rodin wrote: > On Tue, Aug 17, 2010 at 09:52:34PM +0200, Philipp Kern wrote: > > sparc had concerns raised about [its] releasability > http://release.debian.org/squeeze/arch_qualify.html indicates the number of > porters and upstream support is questionable by being yellow, but other than > that there is no real explanation. It would be good if this was clarified, > so that we know what you guys actually expect. Well, for upstream support there is: at the bottom of the page. According to doko sparc32 code generation is unmaintained upstream, and he doesn't want to step up to maintain it any longer. Furthermore I found the following thread dated back to 2007: http://lists.debian.org/debian-sparc/2007/07/msg00049.html So far nobody stepped up to provide us with a working sparc64 port. I know that aurel32 did some work on zee.debian.org, but was hurt by bad RAM in that box (AFAIR). What we are currently struggling with are build failures that happen on one class of the builders, while not happening on the other, and IIRC this is happening vice-versa. Hopefully others can fill in the gaps I left here. Kind regards, Philipp Kern
Attachment:
signature.asc
Description: Digital signature