Bug 166401 - rpmbuild parses tags is spec file strangely
rpmbuild parses tags is spec file strangely
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: rpm (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Paul Nasrat
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2005-08-20 10:18 EDT by Vic
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-08-20 11:04:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Vic 2005-08-20 10:18:05 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040124

Description of problem:
I had an old spec file (i.e. it used to work) which mentioned a change to the "%install" section within the %changelog.

Running this through rpmbuild causes the changelog comment to be parsed as the start of the %install section, and the real %install tag is then seen as a second %install section. rpmbuild then complains about this, and doesn't build anything.

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

How reproducible:

Steps to Reproduce:
1. Put a comment in %changelog saying something about %install
2. Run rpmbuild on that spec file
3. Watch it fail...

Actual Results:  rpmbuild complains & doesn't do anything

Expected Results:  rpmbuild should have built the rpms

Additional info:
Comment 1 Paul Nasrat 2005-08-20 10:46:13 EDT
Macros get expanded everywhere use %%install to escape in changelog, etc

What version of rpm was this known to work with.
Comment 2 Vic 2005-08-20 10:50:26 EDT
Sorry, don't know which version. This file has been sat on my machine for quite
some time :-)

I'll use the %% workaround.

Comment 3 Paul Nasrat 2005-08-20 11:04:20 EDT
It's been like this for quite some time - eg:


It does bite people when they first hit it but once you know that macros are
expanded everywhere (in comments, changelog, etc) then people don't forget.

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