Bug#824011: warzone2100: FTBFS in testing (maybe missing Build-Conflicts)

[Santiago Vila]

On Mon, 16 May 2016, Markus Koschany wrote:

> How come I am not surprised about your reaction and this reminds me of
> the discussion we had about Bullet and the bug you eventually closed.

If you refer to Bug #818148, it was clearly a violation of Policy 4.6,
which says that in case of errors the build must stop.

My mistake (sorry for that) was to file the bug against bullet,
because the problem was really in doxygen:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818379

but other than that, it was completely justified to use serious severity,
because it was a violation of Policy 4.6, a must directive.


If you are looking for parallelisms, I would highlight your refusal to
reproduce the bug following the steps in the bug report itself.

You did that in #818148, and apparently you are doing it again here.

For this bug, here are the steps to reproduce:

> * Create a stretch chroot (with debootstrap).
> 
> * Install debhelper in the chroot. This will automatically install
>  "automake" as a dependency.
>
> * Then try to build warzone2100 with a command line like this:
> 
> sbuild -d stretch -A warzone2100_3.1.1-3

So: Did you manage to reproduce the problem following those steps?

There is also a question still unanswered: Since you suggested me to
remove automake by hand to "solve the problem", would you also tell
someone to install a build-depends by hand in case you forget to put
it in the control file also to "solve the problem"?

Thanks.