Bug 1292578

Summary: rubygem-safemode does not use proper %{?dist} tag
Product: Red Hat Satellite Reporter: Ken Dreyer (Red Hat) <kdreyer>
Component: PackagingAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED ERRATA QA Contact: Kedar Bidarkar <kbidarka>
Severity: medium Docs Contact:
Priority: unspecified    
Version: NightlyCC: bbuckingham, bkearney, ehelms, jyejare, kbidarka, sthirugn
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/9703
Whiteboard:
Fixed In Version: tfm-rubygem-safemode-1.2.3-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 11:09:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1282891    

Description Ken Dreyer (Red Hat) 2015-12-17 20:18:34 UTC
Description of problem:
rubygem-safemode

Version-Release number of selected component (if applicable):
rubygem-safemode 1.2.1-1-sat

How reproducible:
always

Steps to Reproduce:
1. grep ^Release rubygem-safemode.spec

Actual results:
Release includes %{dist}

Expected results:
Release should include %{?dist} (with a question mark)

Additional info:
OpenStack already fixed this on their ruby193-rhos-4.0-rhel-6 branch in dist-git

Comment 1 Bryan Kearney 2015-12-18 16:04:27 UTC
Connecting redmine issue http://projects.theforeman.org/issues/9703 from this bug

Comment 2 Bryan Kearney 2015-12-18 17:01:33 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/9703 has been closed
-------------
Jason Montleon
https://github.com/theforeman/foreman-packaging/pull/572

Comment 8 Kedar Bidarkar 2016-05-26 16:52:11 UTC
checkit]# grep ^Release rubygem-safemode.spec
Release: 1%{?dist}


VERIFIED with sat62-snap(GA)-13.1

Comment 9 Bryan Kearney 2016-07-27 11:09:01 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.

https://access.redhat.com/errata/RHBA-2016:1501