Bug 498848

Summary: yast2 online_update does not display needed update for software mgmt stack
Product: [openSUSE] openSUSE 11.1 Reporter: Heiko Rommel <heiko.rommel>
Component: YaST2Assignee: Michael Andres <ma>
Status: RESOLVED INVALID QA Contact: Jiri Srain <jsrain>
Severity: Blocker    
Priority: P5 - None CC: ast, dmacvicar, dmueller, jsuchome
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: screen shot of yast2 online_update
solver test case

Description Heiko Rommel 2009-04-28 14:05:17 UTC 
I am currently testing the prepared maintenance update of the software mgmt stack for 11.1:

Products: SUSE Linux 11.1 (debug, multiarch)
SAT Patch No: 791
MD5 sum: 4a9f85342c6ca94787fe778e1819b3ec
SUBSWAMPID: 24006
Packager: dmacvicar@novell.com
Tester: rommel
packages: PackageKit PackageKit-debuginfo PackageKit-debugsource PackageKit-devel PackageKit-lang gnome-packagekit gnome-packagekit-debuginfo ...

I am unable to see this update in yast2 online_update.
In contrast, zypper declares this update as needed (and succeeds in installing it):

boxer:~ # export LANG=C
boxer:~ # zypper pch | grep " 791 "
Testupdates           | softwaremgmt                   | 791     | recommended | Needed

Attaching screen shot of yast2 online_update and solver test case in a minute.
Comment 1 Heiko Rommel 2009-04-28 14:07:00 UTC 
Created attachment 288615 [details]
screen shot of yast2 online_update
Comment 2 Heiko Rommel 2009-04-28 14:08:30 UTC 
Created attachment 288616 [details]
solver test case
Comment 3 Michael Andres 2009-04-29 15:46:19 UTC 
Even if the result is unexpected, yast is right and zypper is wrong. 

The problems core is the broken control.xml we shiped on our install media. This control.xml introduces repository priorities at install time. This way, the official online update repo gets priority 20 (high), while the Testupdates repo you added later, got the default of 99 (low).

YaST is right, because it ignores the low priority Testupdates if high priority official ones are available.

Zyppers behavior is actually wrong (bug #464458), because it ignores the priorities.


Using Testupdates, you should use 'zypper lr -d' to check that the repo has the same priority as the other update repos on your system.