Re: Bug#495400: apr_1.3.2-3(m68k/experimental): test suite fails
On Sat, Aug 05, 2017 at 12:01:53AM +0200, John Paul Adrian Glaubitz wrote: > On 08/04/2017 11:23 PM, Stefan Fritsch wrote: > > 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. > > If no email is send to inform any of the porters, no one is going > to know that there is an actual bug which needs to be worked on. To be fair, the bug was filed by a porter (me), so hrm. -- Could you people please use IRC like normal people?!? -- Amaya Rodrigo Sastre, trying to quiet down the buzz in the DebConf 2008 Hacklab
Re: Bug#495400: apr_1.3.2-3(m68k/experimental): test suite fails
On 08/04/2017 11:23 PM, Stefan Fritsch wrote: > 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. If no email is send to inform any of the porters, no one is going to know that there is an actual bug which needs to be worked on. The port-specific mailing lists exist for this very reason. You can't expect us to know about every bug filed on any package within Debian. If you have a problem with architecture X, talk to the people maintaining it. >> 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? I'm not sure what the current status here is. James Clarke will know more. He's been working on bringing these features to Debian Ports. There is already a transition tracker for Debian Ports: > https://ben.jrtc27.com/ > And the build log [1] seems to be built with "notest" so it does not help > for checking if the test failure still happens. I can test that. There is also a way to set up your own m68k environment [1]. Adrian > [1] https://wiki.debian.org/M68k/sbuildQEMU -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Bug#495400: apr_1.3.2-3(m68k/experimental): test suite fails
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 > >
Re: Bug#495400: apr_1.3.2-3(m68k/experimental): test suite fails
> 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? 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. Adrian > [1] > https://buildd.debian.org/status/fetch.php?pkg=apr&arch=m68k&ver=1.6.2-1&stamp=1501871250&raw=0 -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
