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

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.

In the last weeks we identified several of those wrongly marked files. People seem to follow rpmlint blindly :-) So if you package files in /etc, ask yourself if the user is really supposed to modify the file or not. %config (noreplace) should be used sparingly. At least until we get sth. comparable to debconf.

...

Probably, YaST2 should not trust this file but always force correct value according to currently installed version. OTOH as long as it is offered as user editable one in YaST2 behavior is correct.

Confused ... :) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

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

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

...

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

...

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.

At least I have still /etc/default/grub.{old, rpmsave} hanging around although I never changed grub2 config or actually used it.

Well, it may be discussed whether this file should be shipped at all, but it does not change the original problem.

...

...

In the last weeks we identified several of those wrongly marked files. People seem to follow rpmlint blindly :-) So if you package files in /etc, ask yourself if the user is really supposed to modify the file or not. %config (noreplace) should be used sparingly. At least until we get sth. comparable to debconf.

...

Probably, YaST2 should not trust this file but always force correct value according to currently installed version. OTOH as long as it is offered as user editable one in YaST2 behavior is correct.

Confused ... :) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

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.

On 03/18/2013 06:49 PM, Kyrill Detinov wrote:

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

...

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.

We have a rpmconfigcheck service. Its log is /var/log/update-messages.

While I know about that service, this one-shot service doesn't seem to be invoked anymore. Of course you can run it by hand but I doubt that this is well known. Lastly, you can achieve the same results by doing: $ sudo find /etc /usr/share -name "*.rpm*" I still believe this better belongs into libzypp/zypper so I CC'd some knowledgeable guys ;-) -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

В Thu, 21 Mar 2013 12:19:31 +0100 Michael Andres пишет:

On Tuesday 19 March 2013 09:51:42 Sascha Peilicke wrote:

...

On 03/18/2013 06:49 PM, Kyrill Detinov wrote:

...

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

...

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.

Actually libzypp has code checking for rpmnew/rpmsafe. Maybe something broke here.

I do not think this is relevant for this so far. Once more - GRUB_DISTRIBUTOR is user-editable field. So it will be wrong to replace it with (new) default on update. As example, just recently it was recommended to (mis-)use GRUB_DISTRIBUTOR on UEFI system to allow two openSUSE installations in parallel to have own UEFI boot menu entries. Because they are derived from GRUB_DISTRIBUTOR as well. So the first decision that needs to be done - whether user is allowed to set this variable at all. Or may be that menu title should depend on something else. I think this discussion should better be moved to bugzilla where there is open bug report. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

El 18/03/13 14:49, Kyrill Detinov escribió:

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

...

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.

We have a rpmconfigcheck service. Its log is /var/log/update-messages.

That needs to be removed.. that functionality belongs to zypp and not to a init script... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

In data domenica 17 marzo 2013 23:13:31, Andrey Borzenkov ha scritto:

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

Done ! # 810055 How to fix menu voices ? Daniele. -- *** Linux user # 198661 ---_ ICQ 33500725 *** *** Home http://www.kailed.net *** *** Powered by openSUSE *** -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org