| 2010-04-16 17:17:43 |
Daniel Richard G. |
bug |
|
|
added bug |
| 2018-11-29 14:55:32 |
Scott Moser |
grub2 (Ubuntu): status |
New |
Confirmed |
|
| 2018-11-29 15:04:36 |
Scott Moser |
attachment added |
|
recreate.sh: recreate the bug easilily. https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/564853/+attachment/5217386/+files/recreate.sh |
|
| 2018-11-29 15:08:51 |
Scott Moser |
attachment removed |
recreate.sh: recreate the bug easilily. https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/564853/+attachment/5217386/+files/recreate.sh |
|
|
| 2018-11-29 15:09:05 |
Scott Moser |
attachment added |
|
recreate.sh: recreate the bug easilily. https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/564853/+attachment/5217387/+files/recreate.sh |
|
| 2018-11-30 22:59:17 |
Daniel Richard G. |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812574 |
|
| 2018-11-30 22:59:17 |
Daniel Richard G. |
bug task added |
|
grub2 (Debian) |
|
| 2018-11-30 23:24:17 |
Bug Watch Updater |
grub2 (Debian): status |
Unknown |
New |
|
| 2019-01-06 04:05:43 |
Bug Watch Updater |
grub2 (Debian): status |
New |
Fix Committed |
|
| 2019-01-12 09:56:47 |
Bug Watch Updater |
grub2 (Debian): status |
Fix Committed |
Fix Released |
|
| 2019-02-12 13:36:00 |
Francis Ginther |
tags |
|
id-5c5c539ad3b453093101b6b0 |
|
| 2019-03-06 15:20:47 |
Launchpad Janitor |
grub2 (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2019-03-18 18:55:44 |
Mathieu Trudel-Lapierre |
description |
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. |
[Impact]
All users of Ubuntu, especially on updates of the grub packages. (Grub is used nearly everywhere to boot)
[Test case]
== 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. |
|
| 2019-03-19 22:50:08 |
Brian Murray |
nominated for series |
|
Ubuntu Cosmic |
|
| 2019-03-19 22:50:08 |
Brian Murray |
bug task added |
|
grub2 (Ubuntu Cosmic) |
|
| 2019-03-19 22:51:53 |
Brian Murray |
grub2 (Ubuntu Cosmic): status |
New |
Incomplete |
|
| 2019-03-21 19:38:02 |
Mathieu Trudel-Lapierre |
description |
[Impact]
All users of Ubuntu, especially on updates of the grub packages. (Grub is used nearly everywhere to boot)
[Test case]
== 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. |
[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. |
|
| 2019-03-21 20:36:23 |
Brian Murray |
grub2 (Ubuntu Cosmic): status |
Incomplete |
Fix Committed |
|
| 2019-03-21 20:36:26 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-03-21 20:36:27 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2019-03-21 20:36:31 |
Brian Murray |
tags |
id-5c5c539ad3b453093101b6b0 |
id-5c5c539ad3b453093101b6b0 verification-needed verification-needed-cosmic |
|
| 2019-03-21 21:00:48 |
Brian Murray |
bug task added |
|
grub2-signed (Ubuntu) |
|
| 2019-03-21 21:02:03 |
Brian Murray |
grub2-signed (Ubuntu): status |
New |
Fix Released |
|
| 2019-03-21 21:02:08 |
Brian Murray |
grub2-signed (Ubuntu Cosmic): status |
New |
Fix Committed |
|
| 2019-03-21 21:04:25 |
Brian Murray |
grub2 (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2019-03-21 21:04:31 |
Brian Murray |
tags |
id-5c5c539ad3b453093101b6b0 verification-needed verification-needed-cosmic |
id-5c5c539ad3b453093101b6b0 verification-needed verification-needed-bionic verification-needed-cosmic |
|
| 2019-03-21 21:05:44 |
Brian Murray |
grub2-signed (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2019-04-01 21:38:41 |
Mathieu Trudel-Lapierre |
tags |
id-5c5c539ad3b453093101b6b0 verification-needed verification-needed-bionic verification-needed-cosmic |
id-5c5c539ad3b453093101b6b0 verification-done-bionic verification-needed-cosmic |
|
| 2019-04-02 01:06:10 |
Mathieu Trudel-Lapierre |
tags |
id-5c5c539ad3b453093101b6b0 verification-done-bionic verification-needed-cosmic |
id-5c5c539ad3b453093101b6b0 verification-done-bionic verification-done-cosmic |
|
| 2019-04-02 01:10:26 |
Mathieu Trudel-Lapierre |
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. |
[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 /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. |
|
| 2019-04-02 16:13:49 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-04-02 16:14:12 |
Launchpad Janitor |
grub2 (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
| 2019-04-02 16:14:21 |
Launchpad Janitor |
grub2-signed (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
| 2019-04-03 13:21:21 |
Andres Rodriguez |
tags |
id-5c5c539ad3b453093101b6b0 verification-done-bionic verification-done-cosmic |
id-5c5c539ad3b453093101b6b0 verification-done verification-done-bionic verification-done-cosmic |
|
| 2019-04-04 10:00:40 |
Launchpad Janitor |
grub2 (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-04-04 10:00:44 |
Launchpad Janitor |
grub2-signed (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
