<div class="gmail_quote">On Tue, Oct 20, 2009 at 1:36 AM, Tony Nelson <<a href="mailto:tonynelson@georgeanelson.com">tonynelson@georgeanelson.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> If the above seem OK, then: rpm -q python yum # should be python-2.6-xxx, yum-3.2.xxx rpm -V python # should produce no output rpm -V yum # should produce no output or only /etc/yum.conf </blockquote> rpm -q python yum python-2.6-9.fc11.i586 yum-3.2.24-2.fc11.noarch rpm -V python S.5....T. /usr/lib/python2.6/subprocess.pyc Yeah. I'm a little confused by that. So, I checked the date: ll /usr/lib/python2.6/sub* -rw-r--r--. 1 root root 45471 2009-06-08 16:07 /usr/lib/python2.6/subprocess.py -rw-r--r--. 1 root root 119 2009-08-26 21:15 /usr/lib/python2.6/subprocess.pyc -rw-r--r--. 1 root root 32985 2009-06-08 16:07 /usr/lib/python2.6/subprocess.pyo I am baffled as to what would have caused the module to recompile on 8/26. rpm -V yum returns no output. </div>