Bug 117461

Summary:	YaST system upgrade wants to install older kernel
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Michael Stather <kontakt>
Component:	YaST2	Assignee:	Jiri Srain <jsrain>
Status:	VERIFIED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None	CC:	suse-beta, uli.2001
Version:	RC 1
Target Milestone:	---
Hardware:	Other
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	YaST2 Logs

Description Michael Stather 2005-09-16 14:24:57 UTC

I´ve kernel 2.6.13-9 installed (via YOU-Upgrade).
When I use "system upgrade" the package manager wants to install the older
2.6.13-8 version.

Comment 1 Jiri Srain 2005-09-26 10:57:43 UTC

Attach the logs, please. See http://www.opensuse.org/index.php/Submit_a_bug 
for details.

Comment 2 Michael Stather 2005-09-26 11:04:57 UTC

Created attachment 50814 [details]
YaST2 Logs

Comment 3 Jiri Srain 2005-10-21 14:52:43 UTC

Michael A., how does update select packages? Does it check versions somehow, or does it select the package always (even if the version is the same or lower)?

Comment 4 Michael Andres 2005-10-24 10:20:10 UTC

If you grep for kernel in the logs, you'll find:

 PMPackageManager_update.cc(doUpdate):215 
   REPLACEMENT FOR PMPackage(<-4){kernel-default-2.6.13-9.i586[6787]}
   ==> (keep installed)PMPackage(<-45){kernel-default-2.6.13-8.i586[6787]}

I.e installed is kernel-default-2.6.13-9; update decides to keep it; available candidate was kernel-default-2.6.13-8. IMO correct. And the update summary as well lists no downgrades. 


Maybe it's 
  Kernel.ycp:466 Selecting 'kernel-default' as kernel package
or
  clients/update_proposal.ycp:39 Selected kernel: kernel-default,..

where the downgrade is enforced. But I don't see the packagemanager doing this.

Comment 5 Klaus Kämpf 2005-10-24 10:37:08 UTC

Kernel.ycp and clients/update_proposal.ycp only suggest a package _name_ not a version.

Comment 6 Jiri Srain 2005-10-26 07:56:21 UTC

Yes, but the problematic code was in clients/update_proposal (it was there in order to make the update procedure install the correct kernel).

I don't force the kernel package selection any more, which should solve this problem (and also the other 2 bugs about this issue I have :-))

Done in SVN.

Comment 7 Jiri Srain 2005-10-26 07:57:27 UTC

*** Bug 129167 has been marked as a duplicate of this bug. ***

Comment 8 Jiri Srain 2005-10-26 07:58:04 UTC

*** Bug 128369 has been marked as a duplicate of this bug. ***

Comment 9 Christian Boltz 2006-01-05 17:00:05 UTC

I'm able to reproduce this bug in 10.0 final.

Was your SVN version just too late to be included in 10.0 final or does the bug still exist?

Comment 10 Christian Boltz 2006-02-02 23:21:01 UTC

Works as expected in 10.1 beta2 :-)