Bug 156328

Summary: Distro upgrade leaves old packages despite updates on the media
Product: [openSUSE] SUSE Linux 10.1 Reporter: Kurt Garloff <garloff>
Component: InstallationAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED DUPLICATE QA Contact: Klaus Kämpf <kkaempf>
Severity: Major    
Priority: P5 - None    
Version: Beta 7   
Target Milestone: ---   
Hardware: x86-64   
OS: SuSE Linux 10.1   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Kurt Garloff 2006-03-09 00:00:44 UTC 
When upgrading from SUSE Linux 9.1 to SUSE Linux 10.1 beta 7 on x86-64,
I got one package conflict (which was correct), but then looking into
the package installer, I saw that a number of packages that should be
upgraded are not. Most of them have the -32bit suffix and the reason is
that the versioning was 9.1-2004xxxxxxxx there, which is newer than the
version on the install media.

On distribution upgrade, we may need to consider to looking at build dates
or maybe not look at versioning info at all?
Comment 1 Kurt Garloff 2006-03-09 00:03:21 UTC 
It does not only happen for -32bit packages (which have this borken versioning), but also for packages like mkisofs which had version 2.01a27
before and now has 2.01 (final). So it's likely to affect real users ...
Comment 2 Klaus Kämpf 2006-03-09 08:36:46 UTC 

*** This bug has been marked as a duplicate of 155472 ***