Bug 388881

Summary:	rpmlint doesn't complain about empty tags
Product:	[Fedora] Fedora	Reporter:	Stephen Warren <swarren>
Component:	rpmlint	Assignee:	Ville Skyttä <ville.skytta>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	8	CC:	tmz
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	0.82-2.fc8	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-12-21 21:08:24 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 Stephen Warren 2007-11-17 21:19:10 UTC

Description of problem:
If a .spec file contains this line:
Conflicts:
Then rpmlint doesn't complain about it, but rpmbuild won't process the spec file

Version-Release number of selected component (if applicable):
rpmlint-0.81-1.fc8

How reproducible:
Always

Steps to Reproduce:
1. Create a .spec file containing the line "Conflicts:"
2. Run rpmlint on the .spec file
  
Actual results:
No errors/warnings

Expected results:
An error/warning should be produced

Comment 1 Ville Skyttä 2007-11-17 22:19:24 UTC

rpmlint does not have a full featured specfile parser; for specfile syntax
checks you can run eg. "rpm -q --specfile /path/to/foo.spec".

Limitation documented upstream, but as far as I'm concerned, the implementation
is unlikely to change.  http://rpmlint.zarb.org/cgi-bin/trac.cgi/changeset/1383

Comment 2 Fedora Update System 2007-12-07 21:33:25 UTC

rpmlint-0.82-2.fc8 has been pushed to the Fedora 8 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update rpmlint'

Comment 3 Fedora Update System 2007-12-21 21:08:18 UTC

rpmlint-0.82-2.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.