Hi Otto, On Tue, 21 Apr 2020 21:54:57 +0300 =?UTF-8?B?T3R0byBLZWvDpGzDpGluZW4=?= <o...@debian.org> wrote: > I noticed my builds started failing today with error message: > > Step 4/7 : RUN DEBIAN_FRONTEND=noninteractive mk-build-deps -r -i > control -t 'apt-get -y -o Debug::pkgProblemResolver=yes > --no-install-recommends' > ---> Running in 912092c7ebbd > dpkg-buildpackage: info: source package mariadb-10.5-build-deps > dpkg-buildpackage: info: source version 1.0 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by root <root@912092c7ebbd> > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > 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 > 'mariadb-10.5-build-deps_1.0_amd64.deb': No such file or directory > mk-build-deps: dpkg --unpack failed > The command '/bin/sh -c DEBIAN_FRONTEND=noninteractive mk-build-deps > -r -i control -t 'apt-get -y -o Debug::pkgProblemResolver=yes > --no-install-recommends'' returned a non-zero code: 2 > > I am pretty sure this is related to the recent equivs 2.3.0 release, > but I have not figured out the details yet. > > > Run the attached Dockerfile to reproduce.
could you try adding the package build-essential to the "apt-get install" command in your Dockerfile and see if the problem persists? I think the trivial reason for this issue is, that equivs now always uses dpkg-buildpackage (see #880165 or commit c1f8ba) but it didn't add a dependency on build-essential. The build-essential package is only a Recommends of dpkg-dev and thus it is not guaranteed to be installed just by depending on dpkg-dev. Thanks! cheers, josch
signature.asc
Description: signature