[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

packages not built on sparc due to fixed sparc kernel bug



At least four packages (illuminator, fet, scalapack, kmd) are failing
to build on sparc due to a kernel bug that is fixed in the current
sarge versions.  (bugs 136130, 268450, 287287, 307428) Scalapack got
the sparc binary removed to allow it into woody.

Since vore, the sparc buildd, is still running an older kernel, they
fail to build on it.

None of this is an RC issue, since three of the packes don't have
sparc binaries on sarge, and illuminator only developed the
problem recently.

Should these packages be kept out of sarge on sparc, or should
the binaries be built elsewhere?  If the latter, where should the
binaries be uploaded to?  Does TPU accept binary-only uploads?


----- Forwarded message from Jurij Smakov <jurij@wooyd.org> -----
For the record, the following (or later) kernel versions (both currently 
in sarge) are required for the builds to succeed:

kernel-image-2.4.27-2-sparc64 version 2.4.27-2
kernel-image-2.6.8-2-sparc64  version 2.6.8-6

Best regards,

Jurij Smakov                                        jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/                   KeyID: C99E03CC

----- End forwarded message -----

-- 
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: