Yes I forgot the option existed and didn't have the context while writing the comment, but generally speaking debconf is a crapshoot and while it is there and it makes sense to use it accordingly, we certainly should try to avoid introducing more of it.
The file here is a mess, so it's a conffile and the I believe preinst merges the previously configured value into the new file such that you only get promoted about differences in other options, very annoying, and highly fragile. You can easily see this doesn't scale to every possible grub option. Presumably we should introduce /usr/lib/grub/default.d and implement the whole drop in logic with /usr directories which is a goal certainly for all our packages. Then again it is 2024, and people now are highly used to settings made in foo being overriden by settings in foo.d as that's the standard semantic for a wide range of packages, most prominently systemd, so I don't think this is as much of a concern as it was 5 years ago. That being said, of course not mentioning that grub.d exists and overrides settings in the default configuration file is an oversight that certainly should be fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812752 Title: UX: changing GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub has no effect in cloud images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1812752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
