Bug 696950 - RPM editor places macro where should be its value
Summary: RPM editor places macro where should be its value
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: eclipse-rpm-editor
Version: 6.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Alexander Kurtakov
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-15 11:39 UTC by Michal Nowak
Modified: 2013-03-08 02:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-06 12:51:05 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Eclipse Project 351322 0 None None None Never

Description Michal Nowak 2011-04-15 11:39:40 UTC
Description of problem:

Have:

%if 0%{?_buildid}
%define pkg_release 0.%{?_buildid}%{?dist}
%else
%define pkg_release 4%{?dist}
%endif

Version: 1.1.16
Release: %{?pkg_release}

Then did Ctrl-Al-C and got:

%changelog
* Fri Apr 15 2011 newman <newman.redhat.com> 1.1.16-%{?pkg_release}
- 


I guess there should be 1.1.16-4, not the macro itself.

Version-Release number of selected component (if applicable):

eclipse-rpm-editor-0.5.0-2.el6.x86_64

Comment 2 RHEL Program Management 2011-07-06 00:31:23 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 3 Andrew Overholt 2011-07-06 12:51:05 UTC
Upstream bug:  https://bugs.eclipse.org/bugs/show_bug.cgi?id=351322


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