Bug 340922

Please attach y2logs. If you are in doubt follow:

http://en.opensuse.org/Bugs/YaST

Thanks!

Created attachment 184459 [details]
log output from the previous update on Friday

Could you please attach versions of the menu.lst before and after ther update? Thanks.

No, I'm sorry - I can not restore these versions.

So, if I understand you correctly, you had 2 xen entries before the kernel update. One for the "normal" xen kernel and one for a xen-pae one, right?

What if still don't understand is your following comment:

"The update process deleted the command "configfile" that I placed before the
comment line "##YaST - activate" in my previous configuration."

What exactly should this be good for?

(In reply to comment #7 from Alexander Osthof)
> So, if I understand you correctly, you had 2 xen entries before the kernel
> update. One for the "normal" xen kernel and one for a xen-pae one, right?

Yes, this is a standard setting.


> What if still don't understand is your following comment:
> "The update process deleted the command "configfile" that I placed before the
> comment line "##YaST - activate" in my previous configuration."

Is the tool prepared to tolerate additional commands besides the ones that are marked with specific comments?


> What exactly should this be good for?

I want to put additional settings there. The YaST update should keep it.

(In reply to comment #8 from Markus Elfring)
> 
> Is the tool prepared to tolerate additional commands besides the ones that are
> marked with specific comments?

If the commands are supported, it tolerates and even uses them.

Implemented a distinction for various xen kernel names (flavors) and submitted a new package for 10.3, which will most likely appear with the next update.

Thus, closing this bug RESOLVED FIXED.

If related errors still occur, feel free to reopen.

(In reply to comment #9 from Alexander Osthof)
> If the commands are supported, it tolerates and even uses them.

The line for inclusion of my additional configuration data was deleted again.


> Implemented a distinction for various xen kernel names (flavors) and submitted
> a new package for 10.3, which will most likely appear with the next update.

I do not notice a correction after the update for the release "2.6.22.13-0.3".

Created attachment 186533 [details]
GRUB configuration after kernel update for the release "2.6.22.13-0.3".

Created attachment 186534 [details]
log output from an update on Saturday

Created attachment 186544 [details]
reordered GRUB configuration for my personal preferences

released -> RESOLVED FIXED

Which software update will contain these fixes?
The current online update for Linux kernel 2.6.22.16-0.1 shows still open issues.

Created attachment 192634 [details]
GRUB configuration after kernel update for the release "2.6.22.16-0.1"

1. a duplicate title

2. Is it correct to specify "module /initrd-2.6.22.16-0.1-xen" and "module /initrd-2.6.22.16-0.1-xenpae"?
  I would expect the key word "initrd" there as it is used at other places.

3. My include line was deleted again.

4. Why was the part "memtest86+" thrown away?

Created attachment 192635 [details]
log output from an update on Thursday

Sorry, comment #14 was a bit misleading. This was because the fix for this bug went into the maintenance update for SLES10-SP1, but not yet for 10.3.

Please be patient, there will be an online update of perl-Bootloader for 10.3 soon.

Thanks for your notice.

Where was the library corrected?
http://www.novell.com/products/linuxpackages/opensuse/perl-bootloader.html
http://search.cpan.org/~bryce/Linux-Bootloader-1.3/lib/Linux/Bootloader/Grub.pm

I hope that the correction will be published together with the fixes for the issues "CPU frequency scaling not working after upgrade to latest kernel (2.6.22.16-0.1-default)" (Bug #357598) and "cpufreq not supported" (Bug #357516).
It is surprising to get broken updates.

In reply to comment #19:

The first link is a reference to the original perl-Bootloader package from openSUSE 10.3, thus not fixed yet.

The second link is another implementation of a bootloader configurator, but we don't use it in our distro.

This is the link where the (SLES10-SP1 !) update is located:

http://download.novell.com/Download?buildid=ggD7kc_SyrM~

How long will the publication of this fix be delayed for openSUSE users compared to enterprise customers?
Which position has it got in your processing queue?

My apologies, but I'm quite busy these days and resources are limited, too. But the perl-Bootloader update for openSUSE 10.3 is the next item in my queue, so I'm confident to release it soon.

released

I've prepared a new package of perl-Bootloader which should be available soon
as maintenance update for openSUSE 10.3.

Meanwhile, the new perl-Bootloader package (which will be released as
maintenance update) is available via openSUSE Build Service.

http://download.opensuse.org/repositories/home:/aosthof/openSUSE_10.3/

This package should fix this bug, thus closing RESOLVED FIXED.

If related errors still occur, feel free to reopen.

This story continues for the package "perl-Bootloader 0.4.32.21-0.1" under openSUSE 11.x ...

Created attachment 226814 [details]
GRUB configuration after kernel update for the release "2.6.25.9-0.2"

My additional "configfile" line was forgotten once more. It would also be nice if more menu entries will be kept.

Created attachment 226820 [details]
log output from an update on Tuesday

Reassigning to new maintainer of perl-Bootloader.

Created attachment 228220 [details]
reordered GRUB configuration for my personal preferences

I look at this bug and problem is, that from global options p-bootloader store only known and known is that which is shown in yast-bootloader. This bug need more work to consider how change editing global options.

I wonder why it seems to be so hard to support global options (not per title settings) correctly.

Should a configuration line like "module /initrd-2.6.25.9-0.2-xen" also be adjusted?

Why does the software component "perl-Bootloader 0.4.63-2.1" require the release "perl = 5.10.0" by its dependencies?

(In reply to comment #32 from Markus Elfring)
> I wonder why it seems to be so hard to support global options (not per title
> settings) correctly.
> 
> Should a configuration line like "module /initrd-2.6.25.9-0.2-xen" also be
> adjusted?
> 
> Why does the software component "perl-Bootloader 0.4.63-2.1" require the
> release "perl = 5.10.0" by its dependencies?
> 

1) because menu.lst is parsed for known commands and configfile isn't as known (which is mistake, but whole system need improve due to additional negatives). and if I change something in global section, rewrite write only parsed options.

2) http://en.opensuse.org/SUSE_Build_Tutorial#Perl_Packages

I hope I answer all your question. I can provide patch for you, which stop removing configfile section, but final sollution need be more generic (this patch also breaks yast-bootloader in ncurses).

(In reply to comment #33 from Josef Reidinger)
> 1) because menu.lst is parsed for known commands and configfile isn't as known

I find this acknowledgement very interesting. I wonder why my issue was closed even after it was known that it is not completely resolved so far.


> 2) http://en.opensuse.org/SUSE_Build_Tutorial#Perl_Packages

I would hope that the condition "perl >= 5.8.8" (instead of "perl = 5.10.0") would also be sufficient.


> I can provide patch for you, which stop removing configfile section,
> but final solution need be more generic (this patch also breaks
> yast-bootloader in ncurses).

I assume that more system administrators and advanced users are keen on a corresponding fix.

I fix it in svn and test it (and works). So now configfile survive any kernel update. Only problem is comments, which is removed. I try in future also survive all comments in global section.

0.4.70 released, if problem still happen please reopen with actual logs