[Bug 564853] Re: Spurious conffile prompts for /etc/default/grub

[Brian Murray]

Hello Daniel, or anyone else affected,

Accepted grub2 into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/grub2/2.02-2ubuntu8.13
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Also affects: grub2-signed (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: grub2-signed (Ubuntu)
       Status: New => Fix Released

** Changed in: grub2-signed (Ubuntu Cosmic)
       Status: New => Fix Committed

** Changed in: grub2 (Ubuntu Bionic)
       Status: New => Fix Committed

** Tags added: verification-needed-bionic

** Changed in: grub2-signed (Ubuntu Bionic)
       Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/564853

Title:
  Spurious conffile prompts for /etc/default/grub

Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  Fix Released
Status in grub2 source package in Bionic:
  Fix Committed
Status in grub2-signed source package in Bionic:
  Fix Committed
Status in grub2 source package in Cosmic:
  Fix Committed
Status in grub2-signed source package in Cosmic:
  Fix Committed
Status in grub2 package in Debian:
  Fix Released

Bug description:
  [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

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/564853/+subscriptions