From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 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: Always 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:
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.