Bug 232334 - releasever macro is not reporting proper version
Summary: releasever macro is not reporting proper version
Status: CLOSED DUPLICATE of bug 229847
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date   
(Show other bugs)
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Bret McMillan
QA Contact: Brandon Perkins
Depends On:
TreeView+ depends on / blocked
Reported: 2007-03-14 19:58 UTC by Chris Stankaitis
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-05-22 22:10:20 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Chris Stankaitis 2007-03-14 19:58:01 UTC
Description of problem:

Installed a custom yum repository.  My YUM line in rhn/sources is

yum dw-noarch https://yum.URL.net/redhat/$releasever/noarch
yum dw-$basearch https://yum.URL.net/redhat/$releasever/$basearch

My RHEL 4 boxes (U3 & U4) are reporting their releasever as "3" and not "4"

In /usr/share/rhn/up2date_client/sourcesConfig.py a search for releasever turns up

     releasever = up2dateUtils.getVersion()

        releasever = "3"

It would apear you guys have elected to hard code the release version, and this
has not gotten fixed.

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


Actual results:

Fetching Obsoletes list for channel: dw-noarch...

Fetching obsoletes list for https://yum.URL.net/redhat/3/noarch...
Fetching Obsoletes list for channel: dw-i386...

Fetching obsoletes list for https://yum.URL.net/redhat/3/i386...

Expected results:


Comment 1 Chris Stankaitis 2007-03-14 19:59:47 UTC
Can I change that hard-coded releasever in the sourcesConfig.py to "4" without
fracking everything else up?... or is this fix more complicated then that.

Comment 2 Ijaaz A. Ullah 2007-03-14 20:02:12 UTC
google shows me that this was opened at one point in time under:


but it doesn't seem to be accessible anymore?

Comment 3 Red Hat Bugzilla 2007-04-12 02:15:07 UTC
User bnackash@redhat.com's account has been closed

Comment 4 Pradeep Kilambi 2007-05-22 22:10:20 UTC

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

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