Hi josch,

Johannes Schauer wrote:
> > If it's similar as with mk-ci-build-deps above, this is likely a bug in
> > mk-build-deps then, just triggered by equivs.
> 
> Again, I don't want to be confrontational here.

Ok. Already forgotten. :-)

> I don't understand as much
> about equivs as you do. But what I tested is completely independent from
> mk-build-deps. What I tried was running:
> 
> equivs-build /usr/share/doc/equivs/examples/webserver.ctl
> 
> And I got the same error as Otto ("Unmet build dependencies:
> build-essential:native")

Sorry, it took me quite a while to realise that I couldn't reproduce
the problem because even in the "clean" pbuilder chroot (which is
meant for building packages) build-essential is pre-installed and
hence the build succeeds. I of course also have it installed
everywhere else where I work on equivs, too.

Then again, a hard dependency on build-essential which pulls in gcc
and g++ is definitely way too much for equivs which is aimed to be
quick and lightweight.

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.

Will first implement this.

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.

Will likely implement this afterwards.

Will then also merge your autopkgtest checks as they should show as
well that (or if ;-) this variant works.

P.S.: The workaround for now is to install build-essential even if not
used in the end.

                Regards, Axel
-- 
 ,''`.  |  Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Reply via email to