Hi Niels, I missed to incorporate (some of) these parts of the original bug report and had a couple of questions.
> Please recognize `X-DH-Compat` as the canonicalize spelling of that > field (currently it incorrectly triggers `cute-field`) and as an > alternative to `debian/compat`. I've opened an MR for this (`cute-field`). > Related, `debian/compat` be phased out starting with compat 14. If I do not specify compat level in d/control, and have d/compat specifying the compat level as 14, this seems to work fine. What exactly does "phased out" mean here? What changes does lintian need to make? > Note: `lintian` can use `dh_assistant` to determine the compat level > instead of implementing the logic itself for checking various fields and > files (the `export DH_COMPAT` checks for `debian/rules` might still be > necessary). Though, this implies debhelper/13.15+ as a dependency for > it to recognize `X-DH-Compat`. What is the better field to use to detect compat level? Is it `declared-compat-level` or `active-compat-level`? Is there an option to get the value directly instead of json? (saves lintian some parsing) Please let me know. Best, Nilesh
