On Mon, 21 Jan 2019, Thomas Goirand wrote: > > If you still need a machine to reproduce this, please contact me > > privately. > > Unfortunately, last time I tried, I could indeed see the FTBFS, but I > wasn't able to understand why it was happening in your build env and not > the standard one (ie: porter box or my own sbuild setup). As you're > actually paying for the VM to be hosted, I don't dare to ask you to > leave it up, and I'm unsure what to do... :/
This is only something to worry about when I give access to a machine and the maintainer takes not days but weeks to ssh into it and try to debug the problem. I trust that this will not happen here. I've prepared a machine for you. Details in private email. If you don't know what's wrong and a failure in the tests does not indicate that the package is misbuilt, then disabling the test is the only reasonable thing to do. Making the build fail just for fun does not make any sense. However, please take the time to investigate the problem properly, as that's the purpose of offering a test machine. [ BTW: Once again I have to remind you that just sending a message to the nnn...@bugs.debian.org address does *not* reach the submitter. I found this message from you after I saw that a new neutron package propagated to testing and still built unrealiably ]. Thanks.
