Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1132509 - foreman-proxy spec file is using incorrect format
foreman-proxy spec file is using incorrect format
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Packaging (Show other bugs)
6.0.4
Unspecified Unspecified
medium Severity low (vote)
: Unspecified
: Unused
Assigned To: Katello Bug Bin
Elyézer Rezende
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-08-21 09:23 EDT by Bryan Kearney
Modified: 2017-02-23 16:02 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-12 01:15:14 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1592 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 05:04:35 EDT

  None (edit)
Description Bryan Kearney 2014-08-21 09:23:53 EDT
Spec file for foreman is using

Release:        1%{dist}

but it should be

%{?dist}
Comment 3 Bryan Kearney 2014-08-21 10:17:16 EDT
Sorry, this is foreman-proxy spec file. not foreman.
Comment 7 Elyézer Rezende 2015-03-09 12:41:36 EDT
Verified on: Satellite-6.1.0-RHEL-7-20150303.0

Steps to verify:

[root@sat6 ~]# rpm -qi foreman-proxy | grep Release
Release     : 1.el7sat
Comment 8 Bryan Kearney 2015-08-11 09:31:39 EDT
This bug is slated to be released with Satellite 6.1.
Comment 9 errata-xmlrpc 2015-08-12 01:15:14 EDT
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/RHSA-2015:1592

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