Bug 759638 - TPS SRPM Failures Dist Usage Test
Summary: TPS SRPM Failures Dist Usage Test
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: ifd-egate
Version: 5.8
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Bob Relyea
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: 758797
TreeView+ depends on / blocked
 
Reported: 2011-12-02 21:46 UTC by Jenny Severance
Modified: 2012-02-21 05:59 UTC (History)
1 user (show)

Fixed In Version: ifd-egate-0.05-17.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-21 05:59:33 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0214 0 normal SHIPPED_LIVE ifd-egate bug fix update 2012-02-20 15:08:07 UTC

Description Jenny Severance 2011-12-02 21:46:56 UTC
Description of problem:

DIST CHECK: %{dist} found instead of %{?dist} in: ifd-egate-0.05-16.el5.src.rpm.spec 
Release string was: 16%{dist} 
TPSHINT: Release engineering policy is to use %{?dist}. This is a bug in the package being tested, and should be fixed before release. 
end test at Fri Dec 2 16:23:29 EST 2011 on ppcp-5s-m1.ss.eng.bos.redhat.com 


Version-Release number of selected component (if applicable):
ifd-egate-0.05-16.el5.i386

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 3 Bob Relyea 2011-12-03 00:32:52 UTC
now fixed in ifd-egate-0.05-17.el5.

Comment 5 Jenny Severance 2011-12-21 16:24:07 UTC
This is verified.

Comment 7 errata-xmlrpc 2012-02-21 05:59:33 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0214.html


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