[opensuse-factory] Re: after dup fro 12.2 to 12.3 grub menu still 12.2

On Mon, 18 Mar 2013 13:03, Sascha Peilicke wrote:

On 03/18/2013 11:27 AM, Andrey Borzenkov wrote:

...

On Mon, Mar 18, 2013 at 12:19 PM, Sascha Peilicke

...

Am 18. März 2013 08:58:55 schrieb Andrey Borzenkov :

...

On Mon, Mar 18, 2013 at 11:49 AM, Sascha Peilicke

...

Am 17. März 2013 20:13:31 schrieb Andrey Borzenkov :

...

В Sun, 17 Mar 2013 19:13:43 +0100 Daniele пишет:

> Hi guys, I'm not a big fun of zypper dup but I did it ! > New system is up and running but grub menu still show 12.2 > instead of 12.3. > Under Yast, boot loader options: > Distributor and Default section -> openSUSE 12.2 > > Is a known issue ? worth a bugreport ?

I'm not sure if it is a known issue so bug report makes sense.

> Better way to fix menu entry ? > I never touched grub 2 configuration files...

The problem is, it takes Distributor from /etc/default/grub (GRUB_DISTRIBUTOR) which is marked as configuration file and so is not changed when package is updated.

From my POV, this wrong. The file should be marked as %config instead. This way, user modifications are not lost but you'll always get the distro defaults.

But this file holds YaST2 bootloader configuration in case of grub2. You cannot simply overwrite it on every update.

Well, how often is grub2 updated?

Every time new openSUSE version is released. And we had 4 or 5 maintenance updated in 12.2. And it is enough to have one which screws up user configuration.

...

Also, I suppose its regenerated rather often anyway.

No. It is setup initially by YaST2 and probably never touched. It is *the* source of grub2 config. grub.cfg is generated *from* /etc/default/grub. [...]

So you have to choose the death you want to die. Either it's user modifications first and the risk that he'll never discover /etc/default/grub.rpmnew (and maybe miss even important stuff) or it's distro defaults first and an annoyed user that has to merge /etc/default/grub.rpmsafe all the time. I'm inclined to prefer the latter because we as distributors can fix up things more easily, but it's debatable of course.

Either way, libzypp/zypper could benefit from a patch that warns the user if a rpmnew/rpmsafe file was created. This way you at least raise awareness.

+1 on the warning for the user for rpmnew/rpmsafe files. That would be really nice to have. On Topic: grub2 "could" do the check on update of bootloader itself. e.g. get the real string from /etc/SuSE-release to replace a pseudo string "$release: [/path/to/release-file]$" Such a patch should have a chance to get in upstream. (Distro independent, Release independent) That way it stays on top, no matter the "zypper dup" around it. OTOH, YaST2 also should do the check and replace in case of mis-match. (Release-file newer than Grub-file -> check "release"-string.) - Yamaban.