Bug 250986

Summary:	/etc/xinetd.d/telnet should be marked as noverify in the specfile
Product:	Red Hat Enterprise Linux 5	Reporter:	David Kovalsky <dkovalsk>
Component:	rpm	Assignee:	Panu Matilainen <pmatilai>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	5.0	CC:	benl
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-09-04 07:00:27 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 David Kovalsky 2007-08-06 11:44:31 UTC

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

Description of problem:
When the xinetd telnet config file is modified, RPM verify test fails. Since the
nature of config files is to be modifiable by the user, it should be marked as
no verify in the spec file. 

This affects automated TPS  test done by URT. Since we have telnet setup on
stable systems all of the TPS tests fail, so having this fixed would save us
some false positives.


Version-Release number of selected component (if applicable):
telnet-server-0.17-38.el5

How reproducible:
always

Comment 1 Adam Tkac 2007-08-31 08:44:57 UTC

reassigning to rpm because it doesn't make sence change %config directive in all
packages. Attributes like MD5, size, mtime won't be checked if %config directive
is specified by default

Comment 2 Panu Matilainen 2007-08-31 09:22:40 UTC

Um, no. Users and especially sysadmins very much want to know if a configuration
file was modified from the shipped package defaults. If you don't want to know
about config file changes, filter them out of the verification results.

Making filtering easier is something I'm willing to consider for future rpm
versions, otherwise WONTFIX.