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

[Andrej Shadura]

Hello,

On Wed, 10 Jun 2020 20:52:37 +0200 Axel Beckert <abe at debian.org> wrote:
> Guillem Jover wrote:
> > > 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. :)

> Argh! It could have been so simple! Thanks!
> 
> Unfortunately I just uploaded a new equivs version less
> than a day ago.
> 
> Will convert this from -d to this anyway with the next upload.
> 
> Will though probably wait until the current version has been migrated
> to testing due to the RC bug fix. (Although this is the better fix for
> that issue.)

Can we bring the -d back? This break a workflow I’ve been depending on 
for quite a few years.

I use equivs to build empty packages to use in integration tests for 
OBS. They need to have dependencies between them, but none of them are 
part of Debian, and none of them are installed in the container that 
runs the test runner script. With no way to add -d, building of the 
package always fails.

     : Now create an empty dependent package in the public project
     cat > public-pkg.equivs <<EOF
     Package: public-pkg
     Build-Depends: debhelper-compat (= 12), hidden-pkg
     EOF

     equivs-build --source public-pkg.equivs

-- 
Cheers,
   Andrej