Verification-done for cosmic: ubuntu@noted-fish:~$ dpkg -l grub\* | grep ii ii grub-common 2.02+dfsg1-5ubuntu8.3 amd64 GRand Unified Bootloader (common files) ii grub-efi-amd64 2.02+dfsg1-5ubuntu8.3 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 version) ii grub-efi-amd64-bin 2.02+dfsg1-5ubuntu8.3 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 binaries) ii grub-efi-amd64-signed 1.110.3+2.02+dfsg1-5ubuntu8.3 amd64 GRand Unified Bootloader, version 2 (EFI-AMD64 version, signed) ii grub2-common 2.02+dfsg1-5ubuntu8.3 amd64 GRand Unified Bootloader (common files for version 2)
As for bionic; with the new version, there are no conffile prompts for the same grub.cfg manipulations that would have normally resulted from a prompt. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic ** Description changed: [Impact] All users of Ubuntu, especially on updates of the grub packages. (Grub is used nearly everywhere to boot) [Test case] == Upgrade prompting == 0) Install Ubuntu - 1) Modify /etc/default/grub.cfg options - 2) Copy /etc/default/grub.cfg to /var/lib/grub/ucf/grub.previous - 3) Update grub to the new package + 1) Modify /usr/share/grub/default/grub options + 2) Run 'sudo apt install --reinstall grub-pc ((or grub-efi-amd64)) Verify that the user IS prompted to approve grub.cfg changes due to changes in the template coming from the process. == User-specified changes == 0) Install Ubuntu 1) Modify /etc/default/grub.cfg options 2) Update grub to the new package Verify that the user is not prompted to approve grub.cfg changes unless the grub2 package unless the grub packages have changed the contents of the default grub.cfg. == Post-deployment upgrades on MAAS-controlled system == 0) Deploy a system using MAAS 1) Update grub to the new package Verify that the user is not prompted to approve grub.cfg changes unless the grub2 package unless the grub packages have changed the contents of the default grub.cfg. [Regression potential] Pay attention to prompting behavior on grub updates as well as any failure to update the grub* packages. Prompting should be limited to the cases where the grub2 source package has changed the contents for the default provided grub.cfg; and on MAAS-controlled systems, the local modifications have changed in some way from the original copy of grub2 installed on the system. --- Binary package hint: grub-pc This concerns grub-pc 1.98-1ubuntu5 in Lucid beta1 (upgrading from 1.98-1ubuntu4). I have a locally modified /etc/default/grub file. When I upgraded to this version of grub-pc, I got the "A new version of configuration file /etc/default/grub is available, but the version installed currently has been locally modified. What do you want to do about modified configuration file grub?" question. The problem is, when I look at the diff, it just shows the differences between my file, and the way it was originally. In other words, the upgraded package does not include any updates to this file; its "pristine" copy of /etc/default/grub is the same as the previous version's. So I shouldn't even be getting a conffile prompt in the first place---as far as the administrator is concerned, nothing has changed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/564853 Title: Spurious conffile prompts for /etc/default/grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/564853/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
