>> The standard rules for debconf are that changes in the filesystem are more important than those in the debconf database
Yes and this is monitored via ucf tools, as shown in sample config scripts (preinstall and postinstall). Thus, if I have changed /etc/default/grub , then ucf will see my changes and would prevent them from being overwritten by automated updates/upgrades (creating grub.ucf-dist file, or providing 3-way merge or any other way it can offer). If I somehow decided to overwrite my /etc/default/grub changes I have to direct ucf to forget about monitoring (via ucfr tool - just removing package config file from internal ucf list) , and then dpkg-reconfigure will successfully overwrite my changes using already preseeded parameters from debconf database. I assume this way is legal, while voluntary unconditional update of debconf database is not, especially with those parameters which I whould like to recover. A typical situation is when I have changed one line in /etc/default/grub and got errorneous boot process, which I want to recover. With your code in grub-pc.config any ucf related things are just disconnected from being partify in this configuration process, and with your code I can recover only that errorneous modified version, since that errorneous parameter is already propagated into debconf database, and this looks like a nonsense action. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090768 Title: grub-pc.config prevents replacing with new config file contents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1090768/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
