* Michael Stone ([EMAIL PROTECTED]) [070120 14:08]: > On Sat, Jan 20, 2007 at 10:20:50AM +0100, Andreas Barth wrote: > >The package failed on the buildd with the error below, please see > >http://buildd.debian.org/fetch.cgi?&pkg=coreutils&ver=5.97-5.2&arch=s390&stamp=1162820579&file=log > >for the full log. > > > >According to waldi, this is probably due to the fact that the unstable > >chroot is bind-mounted to the place where the buildd chroots into. > > So it's a build environment problem. Try building it in a different > environment. I've tried to engage the s390 people over this previously > and haven't gotten anywhere; I'm not sure what else I can do. The test > is there for a reason, to make sure that the tools aren't broken. There > is definately an invalid result being returned on that platform, so the > test fails. I don't have any ability to debug this since I can't > duplicate it on any other platform and I don't have an s390. IIRC, I > tried building it manually before and it worked fine...
On the thread in debian-release, in http://lists.debian.org/debian-release/2007/01/msg00972.html | The following informations are from memory. The test fails if it reaches | a bind mount on the same device. I reproduced it somehow with | | mkdir test1 test2 | | mount --bind test1 test2 | | cd test2 | | call testsuite perhaps this information helps you? (Or anyone else who is chasing this bug) [BTW, the main reason for me submitting this bug is that we have one central place where all the information is stored] Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
