Control: retitle -1 debhelper: -v vs. DH_VERBOSE Marc Haber: > Package: debhelper > Version: 13.6 > Severity: minor > > Hi, > > while debugging a package build process, I would have liked to see what > debhelper does with dpkg-buildflags. Setting DH_VERBOSE didn't give any > results, so I chmodded dpkg-buildflags to 000. This shows that debhelper > calls dpkg-buildflags but doesn't show that in DH_VERBOSE mode: > > [...] > > I think that those calls should be part of verbose output, and it should > be shown what debhelper does with dpkg-buildflag's output. > > Greetings > Marc > > [...] >
Hi Marc, Thanks for the suggestion. My answer is going into several directions here. First off, DH_VERBOSE (or --verbose) has conflicting documentation. I will amend that and close this bug with it. My understanding is that the definition from --verbose is prevailing, but I will check up on that. Secondly, debhelper does *not* call dpkg-buildflags /directly/, so you would not see a call either way. Instead, debhelper uses the Dpkg::Buildflags module to emulate the call. But for the sake of understanding, you can assume the call is pretty much the equivalent of: eval $(dpkg-buildflags --export=sh) Which leads us to an implicit the question - if debhelper does not call dpkg-buildflags, then what are the "/bin/sh: 1: dpkg-buildflags: Permission denied" lines you are seeing? In the sudo package, those would come from /usr/share/dpkg/default.mk (via /usr/share/dpkg/default.mk in debian/rules). Those files are provided by dpkg and therefore beyond the scope of what DH_VERBOSE or debhelper can help you with. I hope this email answered your question to satisfaction and led you to the root of your issue. Thanks, ~Niels
