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 513075 - dist macros don't meet fedora's packaging guidelines
Summary: dist macros don't meet fedora's packaging guidelines
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: redhat-release-server
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Andrew Thomas
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-21 21:23 UTC by Dennis Gilmore
Modified: 2016-01-18 16:09 UTC (History)
3 users (show)

Fixed In Version: redhat-release-6-6.0.0.10
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 594986 (view as bug list)
Environment:
Last Closed: 2010-11-11 14:54:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dennis Gilmore 2009-07-21 21:23:53 UTC
Description of problem:
fedoras packaging guidelines state that el<version> should be defined to 1 
https://fedoraproject.org/wiki/Packaging/DistTag#Conditionals

redhat-release defines the disttag to .el6 and rhel to 6  but is missing el6  defined to 1 



Version-Release number of selected component (if applicable):
redhat-release-6-6.0.0.7.i586

How reproducible:

always 

Steps to Reproduce:
1. install system 
2. cat /etc/rpm/macros.dist
3.
  
Actual results:
%rhel 6
%dist .el6

Expected results:
%rhel 6
%dist .el6
%el6  1

Additional info:

Comment 2 RHEL Program Management 2009-07-21 21:48:22 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 3 Dennis Gregorovic 2009-09-16 02:20:05 UTC
Fixed in redhat-release-6-6.0.0.10

Comment 4 releng-rhel@redhat.com 2009-10-28 15:51:11 UTC
Fixed in 'redhat-release-6-6.0.0.10'. 'redhat-release-6-6.0.0.15' included in compose 'RHEL6.0-20091027.3'.
Moving to ON_QA.

Comment 5 Alexander Todorov 2010-05-18 13:47:18 UTC
With redhat-release-workstation-6-6.0.0.27.el6.x86_64

The file /etc/rpm/macros.dist defines the macros as specified in Fedora packaging guidelines:

%rhel 6
%dist .el6
%el6 1

Moving to VERIFIED.

Comment 6 releng-rhel@redhat.com 2010-11-11 14:54:58 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.