On Fri, 4 Aug 2017, John Paul Adrian Glaubitz wrote: > > Not sure if m68k is alive anymore. The build log urls are not reachable > > anymore this bug report is no longer useful. Closing. > > Well, maybe you should just ask people instead of just closing bug > reports without further notice? > > > I doubt that anyone is interested in debugging m68k issues > > How do you know without sending an email to debian-68k@l.d.o?
The bug has been open for 9 years and no m68k porter has looked at it. Ususally apr test failures are toolchain/kernel/libc issues, so my motivation to debug this for a very slow arch that has zero chance of ever being part of a Debian release is very small. > Here's a current build log [1]. m68k is alive and kicking with full > C++11 support and over 10700 out of 12000 packages being up-to-date. Sorry, I did not know that the ports use the official buildd website nowadays. Is there some tool like rmadison but that includes all inofficial ports, too? And the build log [1] seems to be built with "notest" so it does not help for checking if the test failure still happens. Cheers, Stefan > Adrian > > > [1] > > https://buildd.debian.org/status/fetch.php?pkg=apr&arch=m68k&ver=1.6.2-1&stamp=1501871250&raw=0 > >
