Bug#887902: qtwebchannel-opensource-src: FTBFS with cmake installed

[Daniel Schepler <dschepler@gmail.com>]

On Tue, Feb 20, 2018 at 2:47 PM, Lisandro Damián Nicanor Pérez Meyer
<perezmeyer@gmail.com> wrote:
> As far as I see this bug could be "please add cmake to Build-Conflicts", but
> in that case policy says a package *can* declare relationships (policy 7.7).

Well, that would be one possible solution, but IMO the least preferred
solution, as I consider Build-Conflicts the option of last resort.
Other options, of course, would be to fix the test case (best), or
either skip the test or ignore failures (middle).

(And then if the test case is fixed, it would certainly make sense to
add "Build-Depends: cmake <!nocheck>".)

> I don't see anything that justifies it to be RC. I'm so downgrading the
> severity.
>
> If I missed something in policy, please do not heasitate to reply (but not
> increasing the severity until we check it).

Well, I guess https://release.debian.org/buster/rc_policy.txt doesn't
explicitly state this:

-----
4. Autobuilding

Packages must list any packages they require to build beyond those
that are "build-essential" in the appropriate Build-Depends: fields.

...

Packages must autobuild without failure on all architectures on
which they are supported. ...
-----

But still, my interpretation of the spirit is that the Build-Depends
and Build-Conflicts together have to be sufficient to ensure the
package builds both successfully and correctly.  And that there's no
requirement that everybody building it must necessarily be using a
minimal chroot, or even any chroot at all.  (Otherwise, what would the
purpose of Build-Conflicts be in the first place?)
-- 
Daniel Schepler