Steve Langasek <[EMAIL PROTECTED]> writes: > On Tue, Mar 13, 2007 at 03:30:41PM +0100, Aurélien GÉRÔME wrote: >> On Mon, Mar 12, 2007 at 12:24:49PM -0700, Steve Langasek wrote: >>> Which means someone needs to break this down to show what the testsuite >>> failure is and why it fails. >> As I really cannot reproduce it on several PowerPC subarchitectures >> which I have access to, is it possible to get more information about >> the buildd setup? > I have no idea what information would be relevant. The testsuite output is > gnarly, and it's not clear to me which test suite failures here are fatal. > For all I can see, the problem could be caused by trying to write to > /root,
Nope, that's not it. > or it could be caused by an altivec problem. The first of these is > definitely a bug in this package (it should be cleaned up to use a local > home directory while building), the second could be any number of places, > but a clearer picture of /what/ is failing seems necessary first. I haven't been able to reproduce this problem *anywhere* and upstream hasn't seen a report about a problem like this. I'll probably do another gstreamer-perl upload to get more verbose output from this test, but the test suite helpers in perl are really not helping when it comes to get verbose error messages :-/ Marc -- BOFH #397: T-1's congested due to porn traffic to the news server.
pgpsP3sSKHech.pgp
Description: PGP signature
