Bug 626481 - ypbind rpm test fails on configfile
ypbind rpm test fails on configfile
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: ypbind (Show other bugs)
4.9
All Linux
low Severity medium
: rc
: ---
Assigned To: Karel Klíč
qe-baseos-daemons
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-23 12:23 EDT by Juraj Marko
Modified: 2015-08-31 23:37 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-02-22 09:50:28 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Juraj Marko 2010-08-23 12:23:41 EDT
Description of problem:
rpm verification fails for ypbind

Version-Release number of selected component (if applicable):
ypbind-1.17.2-14
ypbind-1.17.2-13

How reproducible:
100%

Steps to Reproduce:
1. install ypbind
2. edit /etc/yp.conf
3.# rpm -V ypbind-1.17.2-14
  S.5....T. c /etc/yp.conf
  
Actual results:
fails after edit configfile

Expected results:
not fails after edit configfile

Additional info:
http://nest.test.redhat.com/mnt/qa/scratch/ppcp-4as-v1/2010:9711/tps/tps-rpmtest.html
Comment 1 Karel Klíč 2010-09-06 09:51:09 EDT
Why should `rpm -V ypbind` suppress the information that the config file has been changed from what is in the RPM file?
Comment 2 Ondrej Vasik 2011-02-22 09:50:28 EST
This is not a bug, rpm should notify the user about the change. Config file is marked noreplace in spec file, so the user's configuration will not be replaced by update. Expected behaviour of noreplace flag.

Note You need to log in before you can comment on or make changes to this bug.