Strange package checksum report

Dag-Erling Smørgrav des at des.no
Sun Jan 25 01:48:10 UTC 2015


Garrett Wollman <wollman at csail.mit.edu> writes:
> Checking for packages with mismatched checksums:
> p5-XML-SAX-0.99_2: /usr/local/lib/perl5/site_perl/XML/SAX/ParserDetails.ini

This file is updated whenever you install or remove a SAX parser, so
this is expected.  There are at least half a dozen different Perl SAX
implementations in the ports tree.

> 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 ]

These are Pyhon bytecode files. They are automatically regenerated if
you have write access to them and Python thinks they are stale when it
tries to load them.  Apparently, Python's definition of "stale" is
slightly more complex than just comparing timestamps; they are one of
the reasons why Baptiste gave up reproducible package builds.

Is your clock synchronized with NTP?  Is this a VM?  What is the
underlying filesystem?

DES
-- 
Dag-Erling Smørgrav - des at des.no


More information about the freebsd-security mailing list