Bug#958414: Latest equivs version 2.3.0 breaks mk-build-deps

[Guillem Jover]

Hi!

On Tue, 2020-05-26 at 17:59:33 +0200, Axel Beckert wrote:
> Johannes Schauer wrote:
> > And I got the same error as Otto ("Unmet build dependencies:
> > build-essential:native")

> One idea was to add some logic to automatically decide if we can use
> dpkg-buildpackage or not and if not, fall back to the old method by
> calling debian/rules directly which would partially reopen #880165.
> 
> It seems as if build-essential gets automatically added to the build
> dependencies by Dpkg::Vendor::Debian. So this might even be different
> in other derivative distributions, hence we should neither hardcode it
> as dependency nor should we test of it being installed or not.
> 
> But since equivs nearly never compiles stuff but is for metapackages,
> the simple solution is probably to run dpkg-buildpackage always with
> --no-check-builddeps.

[…]

> A maybe a bit safer variant would be to call dpkg-checkbuilddeps
> beforehand and filter out build-essential if it appears. That way
> around it should hurt way less to hardcode the package name.

You can simply use --ignore-builtin-builddeps. :)

Thanks,
Guillem