Bug 198685

Summary: not considering newer package if arch change to be noarch
Product: [openSUSE] openSUSE 10.2 Reporter: Jonathan Arsenault <jonharson>
Component: libzyppAssignee: Michael Andres <ma>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None CC: andreas.hanke, schubi, suse-beta
Version: Alpha 3   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Jonathan Arsenault 2006-08-11 13:48:40 UTC
When upgrading yast2 wont select a newer package that is now a noarch and that was previously of the platform arch eg: upgrading 10.1 to factory package cpp isnt marked as newer. Only the package of current arch is marked as compatible (eg: keep x86_64 4.1.0 instead of installing noarch 4.1.3).
Comment 1 Jonathan Arsenault 2006-08-11 13:56:00 UTC
same for gcc
Comment 2 Jonathan Arsenault 2006-08-11 14:09:30 UTC
speaking of witch gcc is damnned weird in factory .... so now gcc, gcc-c++, libgcc, libstdc++, etc are all virtual noarch package ... i guess that would be alright but then their deps are totally messed up they should obsolete older version and depend on their equivalent (maybe its just my yast being weird but in 10.1 they dont) had to look by hand a bit and install them manually ...
Comment 3 Jonathan Arsenault 2006-08-11 16:15:42 UTC
Well not really same bug but result from not using factory yast and trying to upgrade with software management only part of the system.

*** This bug has been marked as a duplicate of bug 198722 ***
Comment 4 Jonathan Arsenault 2006-08-11 17:33:42 UTC
well yeah this is even present in factory yast.
Comment 5 Jonathan Arsenault 2006-11-01 06:38:23 UTC
now seem to be really gone in factory
eg: jpackage-utils was correctly marked as newer