Hi, On Thu, Apr 03, 2025 at 10:21:07AM +0000, Herbert Snorrason wrote: > After an upgrade today, resolved appears to have stopped resolving mDNS > queries, > despite previously having done so and still being configured to do so. This > appears to be the result of a new override file that appeared in the > package. Unlike multiple other changes that require action to maintain an > existing configuration, I did not get any sort of alert in the upgrade > process.
This is correct. The Debian Technical Committee asked the systemd maintainers to disable mDNS support in the default configuration. The chosen implementation was to place an override file. > I am aware that I can alter my configuration to override the override, but I > do > have to wonder if it isn't more appropriate for the package to alter the > default > configuration file than to override whatever is in the configuration file. At > the very least, it should be possible to alert users to the need for a > configuration change, rather than assuming that users will know why things > have > broken. The alternative of changing the default at compile time was the method preferred by the Debian Technical Committee, but that was not acceptable by the systemd maintainers. I agree that the disablement deserves a NEWS fragment. Do you use apt-listchanges to display such NEWS? Would that have made you aware of the problem? Would adding a note to Debian's release notes help here? Helmut
