Bug 147341 - RHN reports blank epoch as out of date
Summary: RHN reports blank epoch as out of date
Keywords:
Status: CLOSED DUPLICATE of bug 235244
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Web Site
Version: RHN Stable
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bret McMillan
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-02-07 15:06 UTC by Josh Kelley
Modified: 2007-04-24 18:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-04-24 18:19:14 UTC
Embargoed:


Attachments (Terms of Use)

Description Josh Kelley 2005-02-07 15:06:36 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5)
Gecko/20041107 Firefox/1.0

Description of problem:
It's my understanding that a missing epoch is equivalent to an epoch
number of 0.  For example, up2date will recognize a package with no
epoch as a possible upgrade for a package with an epoch of 0. 
However, the RHN web site says that a package with no epoch is
outdated by a package with an epoch of 0.

For example, samba-3.0.11-1 (no epoch) is considered as being in the
same epoch as samba-3.0.9-1.3E.2:0, so it should be considered an
upgrade to samba-3.0.9-1.3E.2:0.  up2date recognizes samba-3.0.11-1 as
an upgrade to samba-3.0.9-1.3E.2:0, but the RHN web site says that a
host with samba-3.0.11-1 installed is out of date.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install samba-3.0.11-1 from Samba's web site.
2. Run up2date -p.
3. Go to the RHN web site.
    

Actual Results:  RHN says that the host is out of date and should have
samba-3.0.9-1.3E2:0 installed.

Expected Results:  RHN should recognize that the host is up to date.

Additional info:

Comment 1 Matthew Davis 2007-04-24 18:19:14 UTC

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


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