Hi Niels, > On `mscgen/0.20-16`, lintian does no emit `debian-build-system` (not > even a `other` value) meaning that `mscgen` will no longer "count" in > the trends.d.n graph over build systems used by packages. > > From my PoV, I would hope that lintian would instead use the > `Build-Driver` value as `debian-build-system` when it is different from > `debian-rules` (that is the default value). When it is `debian-rules` > (or the field is omitted), then the existing logic could be used as-is.
I am not very familiar with debputy and the ramifications of the Build-Driver field and would like to clarify a few things here: 1. I see mscgen has a B-D on debhelper, and debputy at this time can't function completely independent of dh. So should debian-build-system emit both debhelper and debputy? 2. Are the following tags still applicable with Build-Driver as debputy? - dh-exec-private-helper - maintainer-script-lacks-debhelper-token - weak-dependency-on-misc-depends - package-uses-dh-runit-but-lacks-breaks-substvar - debhelper-compat-virtual-relation - debhelper-compat-file-is-missing - declares-possibly-conflicting-debhelper-compat-versions - executable-debhelper-file-without-being-executable - package-uses-debhelper-but-lacks-build-depends - package-uses-dh-exec-but-lacks-build-depends - no-versioned-debhelper-prerequisite - missing-build-dependency-for-dh-addon - python3-depends-but-no-python3-helper - sphinxdoc-but-no-sphinxdoc-depends 3. On what conditions should "package-does-not-use-debhelper" be emitted when Build-Driver is debputy? 4. Related to point "2." how would dh-addons be handled? Does debputy use them internally or an explicit rules is required somewhere? 5. If a Build-Driver contains value other than debputy or debian-rules, should an error be emitted? 6. If a Build-Driver contains a different value than debputy or debian-rules, but has B-D on debhelper, should any of the tags specified in 2. be emitted? Please let me know. Best, Nilesh
