+++ 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
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
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.