https://bugzilla.novell.com/show_bug.cgi?id=302419#c5
Lukas Ocilka changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |visnov@novell.com, jsrain@novell.com
Severity|Critical |Major
Status|NEW |ASSIGNED
--- Comment #5 from Lukas Ocilka 2007-08-23 05:47:19 MST ---
This seems to be undefined behavior without any documentation.
The problem definition is this:
* System before update had installed 'kernel-default'
* During update, solver has selected new 'kernel-default' as a replacement
for the old one.
* Additionally, update has selected new 'kernel-bigsmp' because of new
evaluation which kernel should be selected as default
* As a result, both kernel-default (replaced) and kernel-bigsmp (new)
were installed/updated.
Possible solutions:
1.) Do not select new kernel in case of update (when some kernel-* package
is already selected to be installed/updated).
2.) Force kernel selection by update_proposal and unselect other kernel-*
packages with one exception kernel-xen.
Side effects:
1.) If hardware has been changed, it would not have any effect on the fact
which kernel is selected. Even if the policy has changed between
releases it will not change. That seems to be wrong.
2.) Unselecting all kernels (but the selected one selected by the
update_proposal script and kernel-xen) seem to be a bit tricky.
It should be possible to prefer user-defined selections.
All in all, the solution "1" removes some functionality and the number "2"
might be a bit dangerous when not done correctly. Anyway, the place, where the
fix should be done, is Kernel.ycp, not update_proposal. I'd rather prefer
solution "2".
--
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.