Red Hat Bugzilla – Bug 147341
RHN reports blank epoch as out of date
Last modified: 2007-04-24 14:19:14 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5)
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):
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
Expected Results: RHN should recognize that the host is up to date.
*** This bug has been marked as a duplicate of 235244 ***