Re: [PATCH 1/2] meta: remove dead code from buildchroot script

[Baurzhan Ismagulov <ibr@radix50.net>]

Hello Henning,

On Tue, May 05, 2020 at 01:02:34PM +0200, Henning Schild wrote:
> The first one is a cleanup. And the second one can hopefully help find
> out why bullseye currently does not build anymore.

Thanks. FWIW, at least some of the output leading to the problem can be seen
here:

http://ci.isar-build.org:8080/job/isar_vs_devel_3_fast/9/consoleFull

The relevant part is:

| + mk-build-deps --host-arch armhf -t 'apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends     -y --allow-downgrades ' -i -r debian/control
| dpkg-buildpackage: info: source package isar-exclude-docs-cross-build-deps
| dpkg-buildpackage: info: source version 0.1
| dpkg-buildpackage: info: source distribution unstable
| dpkg-buildpackage: info: source changed by root <root@baighyz.m.ilbers.de>
| dpkg-architecture: warning: specified GNU system type arm-linux-gnueabihf does not match CC system type x86_64-linux-gnu, try setting a correct CC environment variable
|  dpkg-source --before-build .
| dpkg-buildpackage: info: host architecture armhf
| dpkg-checkbuilddeps: error: Unmet build dependencies: build-essential:native
| dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
| dpkg-buildpackage: warning: (Use -d flag to override.)
| Error in the build process: exit status 3
| dpkg: error: cannot access archive 'isar-exclude-docs-cross-build-deps_0.1_armhf.deb': No such file or directory
| mk-build-deps: dpkg --unpack failed
| WARNING: exit code 2 from a shell command.
| 
NOTE: recipe isar-exclude-docs-0.1-r0: task do_install_builddeps: Failed

A possible scenario is that the temporary package created by mk-build-deps now
implicitly or explicitly Build-Depends on build-essential:native, which isn't
installed at the time of dpkg-buildpackage. If we can verify this, we could
install the missing Build-Depends before mk-build-deps.

Which would be a hen-and-egg problem, since mk-build-deps has been introduced
to avoid manual parsing of debian/control fields. The ultimate solution could
be to add all packages to isar-apt and apt-get build-deps e.g. libhello-dev. I
don't know whether that could be done today. Meanwhile, I still think that
parsing the fields is a viable option (with the goal to have the solution
upstream).

With kind regards,
Baurzhan.