Bug 232334 - releasever macro is not reporting proper version
releasever macro is not reporting proper version
Status: CLOSED DUPLICATE of bug 229847
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: up2date (Show other bugs)
4.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bret McMillan
Brandon Perkins
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-03-14 15:58 EDT by Chris Stankaitis
Modified: 2007-11-30 17:07 EST (History)
0 users

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


Attachments (Terms of Use)

  None (edit)
Description Chris Stankaitis 2007-03-14 15:58:01 EDT
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()

        #FIXME:
        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):

up2date-4.4.69-25.i386

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:

https://yum.URL.net/redhat/4/i386...
Comment 1 Chris Stankaitis 2007-03-14 15:59:47 EDT
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 16:02:12 EDT
google shows me that this was opened at one point in time under:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=229847

but it doesn't seem to be accessible anymore?
Comment 3 Red Hat Bugzilla 2007-04-11 22:15:07 EDT
User bnackash@redhat.com's account has been closed
Comment 4 Pradeep Kilambi 2007-05-22 18:10:20 EDT

*** 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.