Bug 137795

Summary: unescaped RPM macro places wrong and confusing text into changelog
Product: [Fedora] Fedora Reporter: Moritz Barsnick <moritz>
Component: mozillaAssignee: Christopher Aillon <caillon>
Status: CLOSED CANTFIX QA Contact: Ben Levenson <benl>
Severity: low Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-04-03 11:33:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Moritz Barsnick 2004-11-01 14:09:23 UTC
Description of problem:
In the SPEC file, there is an unescaped RPM macro which is wrongly 
expanded to its value. A bit confusing, as with every new version of 
the package, it says something else. ;-)

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

How reproducible:
always

Steps to Reproduce:
1. tail +`fgrep -n %changelog mozilla.spec | cut -d: -f1`  mozilla.
spec | fgrep '%{version}'
2. rpm -qp --changelog mozilla-1.7.3-17.src.rpm | fgrep "Update 
Source:"

Actual results:
1. - Update Source: to use %{version}
2. - Update Source: to use 1.7.3

Expected results:
1. - Update Source: to use %%{version}
2. - Update Source: to use %{version}

Additional info:

Comment 1 Moritz Barsnick 2006-10-14 22:39:02 UTC
*ping*
This is still valid for current mozilla packages.

rpmlint should check for unescaped '%' in the %changelog section. :-/

Comment 2 Matthias Clasen 2007-04-01 15:18:07 UTC
mozilla is not in F7 anymore, so I guess this bug should be closed as obsolete.

Comment 3 Moritz Barsnick 2007-04-03 11:33:03 UTC
Ah, wait for packages to die before resolving the bug. ;-))) SCNR.

Yes, it's obsolete, I'm closing it.

By the way, regarding comment #1: This _is_ checked with rpmlint now, AFAICS 
from other packagers' changes. But many don't know how to handle it (escaping 
as "%%" vs. leaving it away.)