RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 604556 - numactl has extra characters after %{?dist}
Summary: numactl has extra characters after %{?dist}
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: numactl
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Neil Horman
QA Contact: Martin Cermak
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-16 08:35 UTC by Daniel Mach
Modified: 2010-11-11 14:51 UTC (History)
5 users (show)

Fixed In Version: numactl-2.0.3-8.1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-11 14:51:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Daniel Mach 2010-06-16 08:35:12 UTC 
There are extra characters after %{?dist} in package release.

actual NVR:
numactl-2.0.3-8.el6.1

correct NVR:
numactl-2.0.3-8.1.el6
Comment 1 RHEL Program Management 2010-06-16 08:53:32 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 2 Bill Nottingham 2010-06-17 20:28:06 UTC 
That's not going to work, as the new version won't upgrade the old.
Comment 3 Bill Nottingham 2010-06-17 20:38:49 UTC 
Never mind comment #2, I always forget where rpm randomly decides not to follow established ordering.
Comment 4 Bill Nottingham 2010-06-17 20:44:56 UTC 
Note that this transformation *only* works if the after-dist-tag bit that you're transposing is numeric.
Comment 5 Neil Horman 2010-06-18 00:11:57 UTC 
Bill, relax, I just upped the release by one to 9.  I'm not sure why the dist tag was the way it was in the first place.
Comment 6 Dennis Gregorovic 2010-06-18 00:31:54 UTC 
It was my fault - the script that I used to bump revisions for automated rebuilds appends a digit to the end.  It needs to be updated to take %{?dist} into account.
Comment 7 Bill Nottingham 2010-06-18 14:24:52 UTC 
(In reply to comment #5)
> Bill, relax, I just upped the release by one to 9.  I'm not sure why the dist
> tag was the way it was in the first place.    

No problem... was mainly a response to the proposed fix that's in 30 or so bugs.
Comment 10 Martin Cermak 2010-09-16 08:11:54 UTC 
=> VERIFIED
Comment 11 releng-rhel@redhat.com 2010-11-11 14:51:54 UTC 
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
Note You need to log in before you can comment on or make changes to this bug.