Niels, https://salsa.debian.org/debian/debhelper/-/commit/b45e5af7e67 feels wrong to me. debhelper still emits this warning for a package that only builds a single binary and is using dh compat 14:
debian/rules binary dh binary dh: warning: Implicitly activating single-binary dh addon for backwards compatibility. In compat 14+, dh: warning: this fallback will *not* happen automatically via dh_auto_install will instead use a dh: warning: different default for --destdir unless the single-binary add-on is active, dh: warning: which can cause the source to produce an empty binary package dh: warning: dh: warning: To keep the existing behaviour (compat 13), please activate the single-binary addon explicitly. dh: warning: This can be done by adding "dh-sequence-single-binary" to Build-Depends or passing dh: warning: --with=single-binary to dh. dh: warning: dh: warning: If you have solved this issue differently (e.g., by passing --destdir explicitly to dh: warning: dh_auto_install or not using dh_auto_install at all) and want to silence this warning dh: warning: without activating the addon, you can do that by passing --without=single-binary to dh dh: warning: to explicitly acknowledge the change. dh: warning: dh: warning: Please see the description of the "single-binary" in "man dh" for more details of what dh: warning: it does and why this is changing from implicit behaviour to explicitly opt-in. Therefore, I use this in my dh compat 14 packages dh $@ --without single-binary I am looking forward to removing "--without single-binary" with dh compat 15. Also, I think there is a grammar error in the warning "this fallback will *not* happen automatically via dh_auto_install will instead use a different default". That looks like 2 phrases, but there is a missing conjunction and maybe a missing subject. Thank you, Jeremy Bícha
