Quack, On 08/21/2017 01:53 AM, Sebastian Andrzej Siewior wrote:
> So if I modify the .conf file only with debconf and then (later) tell > debconf not to handle it then the "old" .conf file will be replaced with > upstream's default one. That's precisely what I did not expect. I can find this upstream example in /usr/share/doc by myself, so I don't see the point in switching to it. It's not like it represents my previous version of the configuration saved when debconf took over (as there was none, first installation). One may wish to use debconf to draft a configuration and then disengage debconf to customize it but it's not possible directly. This may be what people using ucf expect, and in this case you might probably close the bug, but I don't find this a nice behavior. To me disengaging debconf mean: leave as it is, I'll take care of it from now on. I should at least have a choice even if the file was not modified manually yet. The only change which I find legitimate is to remove the "managed by debconf" header. Hope this is clearer. \_o<
signature.asc
Description: OpenPGP digital signature
