Strange package checksum report

[Brian Reichert]

On Fri, Jan 23, 2015 at 11:59:12AM -0500, Garrett Wollman wrote:
> On some of my machines, I've been noticing the following in the
> nightly security mail:

The *.pyc are blobs of byte code that Python generates if the
interpreter chooses to compile a module.

Maybe the package erroneously contains them, and the interpreter
is regenerating them, according to whatever logic is would apply.
Maybe a timestamp issue?

When you do a force reinstall ,what are the timestamps as compared
to the corresponding python modules (*.pl)?



> 
> Checking for packages with mismatched checksums:
> p5-XML-SAX-0.99_2: /usr/local/lib/perl5/site_perl/XML/SAX/ParserDetails.ini
> python27-2.7.9: /usr/local/lib/python2.7/UserDict.pyc
> python27-2.7.9: /usr/local/lib/python2.7/_weakrefset.pyc
> python27-2.7.9: /usr/local/lib/python2.7/abc.pyc
> python27-2.7.9: /usr/local/lib/python2.7/codecs.pyc
> python27-2.7.9: /usr/local/lib/python2.7/copy_reg.pyc
> python27-2.7.9: /usr/local/lib/python2.7/encodings/__init__.pyc
> [ a bunch of other .pyc files elided ]
> 
> Does anyone know what causes this?  Force-reinstalling the package
> fixes it, but only temporarily -- by the time the next security mail
> comes, it's back in this state.
> 
> -GAWollman
> 
> _______________________________________________
> freebsd-security at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-security
> To unsubscribe, send any mail to "freebsd-security-unsubscribe at freebsd.org"

-- 
Brian Reichert				<reichert at numachi.com>
BSD admin/developer at large