Bug 106835

Summary: up2date claims an obsolete package in error
Product: Red Hat Enterprise Linux 2.1 Reporter: Eric Hagberg <hagberg>
Component: up2dateAssignee: Adrian Likins <alikins>
Status: CLOSED NEXTRELEASE QA Contact: Fanny Augustin <fmoquete>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-11-04 20:43:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eric Hagberg 2003-10-11 14:20:58 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
Netscape/7.1

Description of problem:
Every time I run up2date on my AS 2.1 systems, I get this warning message printed.

The following Packages are obsoleted by newer packages:

Name-Version-Release        obsoleted by      Name-Version-Release
-------------------------------------------------------------------------------
XFree86-FBDev-3.3.6-43                  XFree86-compat-modules-3.3.6-43

Both packages are installed on my system (after keeping it fully up2date since
the initial RHAS 2.1 release last May). When updating, I have the packages
pulled down and I manually run "rpm -Uvh *.rpm" against the rpms that are
downloaded, with the exception of kernel rpms, which I "rpm -ivh"... and
manually "rpm -e" the old ones when I'm sure the new kernel is working for me.

Perhaps this is really problem with the channel's definition, but I don't know
what product to log this issue against to get the channel checked, so I've
logged against up2date.

Version-Release number of selected component (if applicable):
up2date-2.8.46.3-1.2.1AS

How reproducible:
Always

Steps to Reproduce:
1. run up2date after keeping AS2.1 machine updated, as described above
2.
3.
    

Additional info:

Comment 1 Adrian Likins 2003-11-04 20:43:19 UTC
should be fixed in next up2date update, up2date wasnt correctly verifying
the version info on obsoletes.