> Peter Samuelson wrote: > > The problem is that I can't reproduce the bug on my platforms, and > > those who can reproduce it (it sometimes happens on kfreebsd) don't > > know ruby. Nor do I, for that matter. There was some effort at > > debugging it awhile back, but it was inconclusive.
[Luk Claes] > Any reason why you don't try the powerpc porter machine? 1) One of the kfreebsd porters was going to get back to me with more debugging, so I let it go. I mostly forgot to ping him. I think he may have just rebuilt and rebuilt until it happened to pass the test (which appears to be a glitch with timestamp conversions, so not 100% repeatable), then uploaded. 2) Between apache2-threaded-dev, kdelibs5-dev, python-all-dev, and f'ing java-gcj-compat-dev, debugging a full build of svn would require asking DSA to install a _lot_ of stuff. I didn't want to do that until I was sure nobody else was already working on this. Anyway I'll ping upstream again, especially now that 1.6.6 is out and the test failures continue - of the two powerpc test failures from before, one just happened on armel and the other happened on kfreebsd-i386. Peter -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
