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

[Santiago Vila]

severity 824011 serious
thanks

On Mon, May 16, 2016 at 02:17:23AM +0200, Markus Koschany wrote:

> I have just rebuilt warzone2100 in a clean sid cowbuilder chroot.

Well, if that's all you did, then I would say that you didn't
understand the nature of the problem.

I'll try to explain better below.

> Everything went fine. Currently automake 1.11 is automatically installed
> but this might change in the future so we should keep an eye on this
> issue. I don't consider this to be release critical at the moment as
> long as warzone2100 can be built from source in a default chroot
> environment but I leave the rest to pabs, if he should feel differently
> about that.

That's precisely the problem: chroots do *not* have to be "default",
and that's precisely why Build-Conflicts exists at all.

Moreover, my chroot was pretty "standard" as it had debhelper installed
by default, nothing really strange.

This is a FTBFS bug. Please read Debian Policy about Build-Conflicts
before modifying severity again.

I'll quote policy for you to save time:

  Build-Depends, Build-Depends-Indep, Build-Conflicts, Build-Conflicts-Indep

     Source packages that require certain binary packages to be installed
     or *absent* at the time of building the package can declare
     relationships to those binary packages.

This is the case here. This package requires normal automake to be
*absent* because it needs automake1.11 and gets confused if there is
another automake floating around.

Thanks.