On 2021-02-02 16:48, Adrian Bunk wrote:
A debhelper compat bump is a breaking change that must not be done
without the maintainer verifying that it didn't introduce any
regression.
This is the whole point of compat levels.
Unfortunately there is a lack of recognition how many bugs are
introduced by blindly updating debhelper compat levels - staying
at a deprecated compat level is better than a not properly tested
compat bump.
To be fair: You can assert statically if the compat bump did not
introduce any changes (by compiling twice).
Kind regards
Philipp Kern
