Bug 1334337

Summary:	%check RPM macro used in %changelog needs to be escaped
Product:	Red Hat Enterprise Linux 6	Reporter:	Kamil Dudka <kdudka>
Component:	nss	Assignee:	Daiki Ueno <dueno>
Status:	CLOSED ERRATA	QA Contact:	Alicja Kario <hkario>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.9	CC:	emaldona, hkario, kdudka, kengert, ksrot, nss-nspr-maint, qe-baseos-security
Target Milestone:	alpha	Keywords:	EasyFix
Target Release:	6.9
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	nss-3.27.1-1.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1332842	Environment:
Last Closed:	2017-03-21 10:26:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1332842
Bug Blocks:

Description Kamil Dudka 2016-05-09 12:14:07 UTC

We have exactly the same bug in RHEL-6 nss, dated back to April 2014:

* Mon Apr 21 2014 Elio Maldonado <emaldona> - 3.15.3-11
- Resolves: Bug 689919 - build without any softoken or util sources in the tree
- Add define-uint32.patch to deal with using older version of nss-softokn
- Fix suboptimal test failure detection shell code in the %check section

Please make sure that the change log is fixed on the next update of nss.

+++ This bug was initially created as a clone of Bug #1332842 +++

Description of problem:
The following change log entry contains unescaped RPM macro, which is not allowed: %check should be spelled as %%check instead.


Version-Release number of selected component (if applicable):
nss-3.21.0-12.el7


How reproducible:
Easily.


Steps to Reproduce:
1. rpmlint nss.spec


Actual results:
[...]
nss.spec:874: W: macro-in-%changelog %check
[...]


Additional info:
This causes problems to csmock (a tool for fully automatic static analysis of RPM packages).

Comment 11 errata-xmlrpc 2017-03-21 10:26:23 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2017-0671.html