Mailinglist Archive: opensuse-bugs (15063 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=309837#c7





--- Comment #7 from Olaf Dabrunz <odabrunz@xxxxxxxxxx>  2007-09-12 12:43:36 MST ---
Thanks for the comments, this helps.

I should add this to the list of things that are strange here:

    - the old entries for openSUSE 10.2 still exist.

These should have been removed when the 10.2 kernel was updated to the 10.3
kernel. The current bootloader_entry script in 10.2 still contains a bug
that prevents the entry from being removed, here is the patch to fix it:

------------------------------------------------------------------
 function update_bootloader()
 {
-       [ -x /sbin/update-bootloader -a "$YAST_IS_RUNNING" != instsys ] ||
return 0
+       [ -x /sbin/update-bootloader ] || return 0
                /sbin/update-bootloader "$@"
 }
------------------------------------------------------------------

Unfortunately, also the upcoming perl-Bootloader patch for 10.2 still
contains this bug (/work/built/patchinfo/510e090e5ef9cf0d15b43f08a8242b20).

One problem down, but needs to be submitted for 10.2.


Next: I understand what happened this far:

    - I only have the standalone logs from perl-Bootloader for the last
      kernel kernel added (2.6.22.5-10-bigsmp). The reason is that the
      update-bootloader script removes the standalone log before adding a
      new entry (AFAICR, in an attempt not to confuse the logs of different
      actions, because no timestamps are recorded with the log entries).

      The new version of perl-Bootloader that I submitted today adds
      pseudo-timestamp and deletes the logfile-removal code.

    - The bigsmp kernel is added after the default kernel during the
      10.3-update, that is the reason for it having the "Original name"
      "linux". So that is OK.


Conclusion: the crucial logs from the update of the "default" kernel (with
the broken "(/dev/hda5)") are still missing. They will only be kept when we
re-test with the version of perl-Bootloader that I submitted today.

Should I test myself (run createrepo and create an extra instsource with the
fresh perl-Bootloader, and hope it will be installed before the kernel
during the update), or should I wait for a new 10.3 build that contains
perl-Bootloader-0.4.24?


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.