tag 904459 + moreinfo
thanks
Hi Andreas,
thank you taking the time to report this bug.
While I fully agree with policy 10.7.3, I don't think policy means this
in the case of using debconf to modify configuration files. Let me
explain why..
* imho policy 10.7.3 means that that no unsupervised
changing of conffiles should happen with the aim,
that any changes to a conffile needs to be approved by the
admin/user, so no silent changes can sneek in/be overwritten.
* netdata uses debconf to ask the user a setting to make the
configuration more suitable for the users use case.
this happens in, depending on the debconf priority/frontend,
an interactive or non-interactive way.
* regardless of it being interactive or not, the way debconf is
used in netdata preserves local modifications in the conffile
and is idempotent.
* imho there is no difference in principle wrt/ 10.7.3 between e.g.
using ucf to handle a configuration update, or use debconf to
change settings like it is done in netdata.
and using ucf clearly is no policy 10.7.3 violation, right?
therefore, I see no (general) violation of policy 10.7.3 here and am
inclined to (unless there are any implementation bugs that I haven't
spottet) close the bug as such.
What do you think?
Regards,
Daniel
