Packages will build approximate a week later as the port updates. So you have for the newest packages different checksums.
pkg check -s
there is a real error somewhere. Unlike some people trying to claim, the checksums are part of the package metadata are not re-fetched from the remote repo at the time of the checking and should always match what is installed on the filesystem. The reasons for the checksum mismatches can be disk corruption at the worst case or it could be an error in the port itself where a file is marked as checksummed but it actually changes during the installation by a pkg-install script. The correct cure in case of corrupted files (followed by a good inspection of the hardware ofc) would be to pkg install -f
the packages with non-matching checksums to forcefully update them from the remote repo and replacing the corrupted files with good ones. If the problem continues you should contact the port maintainer for assistance.If you get a checksum mismatch onpkg check -s
there is a real error somewhere. Unlike some people trying to claim, the checksums are part of the package metadata are not re-fetched from the remote repo at the time of the checking and should always match what is installed on the filesystem. The reasons for the checksum mismatches can be disk corruption at the worst case or it could be an error in the port itself where a file is marked as checksummed but it actually changes during the installation by a pkg-install script. The correct cure in case of corrupted files (followed by a good inspection of the hardware ofc) would be topkg install -f
the packages with non-matching checksums to forcefully update them from the remote repo and replacing the corrupted files with good ones. If the problem continues you should contact the port maintainer for assistance.
I run it on my system, got:
Code:linux_base-c6-6.6_6: checksum mismatch for /compat/linux/etc/ld.so.cache
reinstall does not help.
(On 10.2a, 10.2i, 9.3a and 9.3i. Don't know if this causes problems).