Bug 521622

Summary:	RFE: add documentation about which checks are run
Product:	[Fedora] Fedora	Reporter:	Karel Volný <kvolny>
Component:	rpmlint	Assignee:	Ville Skyttä <ville.skytta>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	11	CC:	manuel.wolfshant, tmz, ville.skytta
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:	2009-09-07 20:30:47 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 Karel Volný 2009-09-07 10:08:01 UTC

Description of problem:
While running rpmlint on a specfile and then on srpm the sets of spec tests differ. It is mentioned within the manpage and the readme file as CAVEATS:

"All checks do not apply to all argument types.  For best check coverage, run rpmlint on source rpms instead of plain specfiles, and installed binary rpms instead of uninstalled binary rpm files."


But there is no list, or reference to other documentation, saying which checks apply for the particular input type. Please add some aid to tell what is going to be checked.

Version-Release number of selected component (if applicable):
rpmlint-0.90-1.fc11.noarch

Comment 1 Ville Skyttä 2009-09-07 20:30:47 UTC

Moved upstream for the same reasons as bug 521628.

http://rpmlint.zarb.org/cgi-bin/trac.cgi/ticket/180

Comment 2 Ville Skyttä 2009-09-08 20:31:42 UTC

By the way, this is not a complete fix for this request, but I just remembered that I had already improved the man page's CAVEATS section somewhat for the next upstream version, it currently says:

"All checks do not apply to all argument types.  For best check
coverage, run rpmlint on all source and binary packages your
build produces.  The set of checks rpmlint runs on source packages
is a superset of the one for plain specfiles, the set of checks
run for installed binary packages is a superset of the one for
uninstalled binary package files, and the source and binary
package check sets are quite different."