On 01/11/14 18:00, Holger Levsen wrote: > Hi, > > On Samstag, 1. November 2014, Ximin Luo wrote: >> I've so far been unable to reproduce this build failure. I've tried doing >> it through cowbuilder, disconnecting from the internet, setting >> `net.ipv6.bindv6only = 1` and `sudo sysctl -p`, and in every case the >> package builds fine. > > you should send this to the bug. >
It is sent to the bug. >> Can you, or anyone else, reproduce it locally? If not, I will have to >> request access to a build porter machine to try to reproduce it. > > it fails to build here too: > https://jenkins.debian.net/userContent/rb-pkg/flashproxy.html > Yes, but it gives me no actionable information. Great, my build is failing, I can't even see the test output or the build environment. :/ >> In the >> meantime I will probably downgrade the severity of this bug so it doesn't >> get autoremoved. > > before I saw this failure on jenkins.d.n I was going to say "sounds > reasonable", now I'm not so sure anymore ;-) OTOH, "fails to build sometimes" > could be justified as just an important bug esp as it should be fixed no > matter the severity :) > It's a slap in the face for my package to be auto-removed, without me even having a chance to fix things. I can't reproduce the bug locally and the build machines don't even output test-suite.log, which is a standard autotools test output file. Can you try building it locally? X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
signature.asc
Description: OpenPGP digital signature
