dpkg-checkbuilddeps and apt-get at odds over libacl1-dev

["Thomas Schmitt" <scdbackup@gmx.net>]

Hi,

i am clueless how to untangle the contradicting perceptions of apt-get
and dpkg-checkbuilddeps about installation state of libacl1-dev.

While running (after debuild -S with normal messages)

  debuild -b

i get

  dpkg-checkbuilddeps: error: Unmet build dependencies: libacl1-dev
  dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
  dpkg-buildpackage: warning: (Use -d flag to override.)

This is doubly strange, because it worked for libisofs 1.4.2-3 before i did
apt-get "update" and "dist-upgrade" today (7 Jul 2016), and because now

  apt-get install libacl1-dev

says

  libacl1-dev is already the newest version (2.2.52-3).

If i use the proposed flag -d

  debuild -b -d

the autotools based detection of libacl headers and .so reports

  checking sys/acl.h usability... yes
  checking sys/acl.h presence... yes
  checking for sys/acl.h... yes
  checking for acl_to_text in -lacl... yes
  enabled  libacl, local processing of ACL

After
  dpkg -i libisofs6_1.4.4-1_amd64.deb
libisofs.so indicates that it is 1.4.4 and willing to operate libacl.

But then in the course of the commands on my cheat sheet

  debclean

goes on strike by

  dpkg-checkbuilddeps: error: Unmet build dependencies: libacl1-dev
  debuild: fatal error at line 1340:
 

Have a nice day :)

Thomas