title: Why does not config(noreplace) create a .rpmnew file on upgrade?
body: <p>I'm currently testing installing a RPM with a config file using the config(noreplace) directive.</p>
  
  <p>As per <a href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch09s05s03.html" rel="nofollow">using config(noreplace)</a></p>
  
  <p>My spec file marks a single file as a config file:</p>
  
  <p><code>%config(noreplace) /opt/lm/dest/conf/db.xml</code></p>
  
  <p>I did an on disk modification to the file for version 1 and proceeded to upgrade to version 2. I was expecting the verbose output to (when using -Uvh) to indicate that it has create a <code>db.xml.rpmnew</code> which it didn't however the on disk modifications I made are intact.</p>
  
  <p>Does anyone know why this might be the case?</p>
  
  <p>Some background info: I am using the same tar file to create both version 1 &amp; 2 which shouldn't make a difference but thought I'd mention it anyway.</p>