Bug 69340 - RHN does not notice obsoleted packages (although up2date does).
Summary: RHN does not notice obsoleted packages (although up2date does).
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Web Site
Version: RHN Stable
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Mike Orazi
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-21 18:23 UTC by Aleksey Nogin
Modified: 2008-10-16 14:49 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-16 14:49:51 UTC
Embargoed:


Attachments (Terms of Use)

Description Aleksey Nogin 2002-07-21 18:23:12 UTC
It appears that if a system contains an obsoleted package, RHN Website would not
lits it as an outdate package and would not count it as an outdated package (and
might show the system as fully updated). 

To reproduce:
create a fully-updated Limbo system and then replace redhat-config-date with
dateconfig (and run up2date -p, obviously). RHN appears to think the system is
still fully updated, but it's wrong.

P.S. up2date hanldes this correctly, only RHN Web site gets it wrong.

Comment 1 Cristian Gafton 2002-08-15 05:35:26 UTC
chip will need to figure this one out.


Comment 2 Amy Owens 2008-10-16 14:49:51 UTC
This bug has been closed due to inactivity.  Please open a new bug with specific details if this problem is still occurring or if an enhancement is needed.


Note You need to log in before you can comment on or make changes to this bug.