Bug 110452 - Version/Release not handled in spec file when they are defined in a "%define" stmt
Summary: Version/Release not handled in spec file when they are defined in a "%define"...
Alias: None
Product: Red Hat Developer Suite
Classification: Retired
Component: RPM Plug-in
Version: 1.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Rick Moseley
QA Contact: eclipse-bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2003-11-19 17:10 UTC by Rick Moseley
Modified: 2007-04-18 16:59 UTC (History)
0 users

Clone Of:
Last Closed: 2004-04-05 20:03:12 UTC

Attachments (Terms of Use)

Description Rick Moseley 2003-11-19 17:10:40 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1)

Description of problem:
Some spec files for RPMs define the version/release numbers in
"%define" statements at the top of the spec file and then the
"Version:/Release:" lines contain those variables instead of
hard-coding them.  The RPM plugin dos not handle those properly.

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

How reproducible:

Steps to Reproduce:
1. Import an SRPM that has the vesion/release numbers in %define
statement (a2ps for example)
2. make a change to the source code and try to export it
3. look at the spec file and notice that now the Version:/Release:
lines have the numbers hard-coded instead of the variables changed

Additional info:

Comment 1 Rick Moseley 2004-04-05 20:03:12 UTC
This fix will be complicated and there are *very* few RPMs that have
their Version/Release numbers defined in variables in their spec
files.  We'll close this for now until there is *much* more demand for
it being fixed.

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