> It's not the apt-news nor esm-cache service that was modified.
> It looks like systemd warns about daemon-reload in any cases if any of the systemd unit files are
> modified and daemon-reload wasn't called after that.
I understand, but in comment #14 the warning is very specific about the unit files that changed: apt-news.service and esm-cache.service
Could it be that something else installed an override config for those units elsewhere (/run, or /etc), and then didn't issue the daemon-reload?
Could we get an "systemctl cat apt-news.service esm-cache.service" output after this warning? It will say which files exactly are being considered, if it's just /lib/systemd/system/{apt-news,esm-cache}.service or other config snippets.
> It's not the apt-news nor esm-cache service that was modified.
> It looks like systemd warns about daemon-reload in any cases if any of the systemd unit files are
> modified and daemon-reload wasn't called after that.
I understand, but in comment #14 the warning is very specific about the unit files that changed: apt-news.service and esm-cache.service
Could it be that something else installed an override config for those units elsewhere (/run, or /etc), and then didn't issue the daemon-reload?
Could we get an "systemctl cat apt-news.service esm-cache.service" output after this warning? It will say which files exactly are being considered, if it's just /lib/systemd/ system/ {apt-news, esm-cache} .service or other config snippets.