Date: Sun, 26 Mar 2023 19:42:04 +0000 From: "Dave Cottlehuber" <dch@skunkwerks.at> To: "E. Seibert" <jerry@seibercom.net> Cc: questions@freebsd.org Subject: Re: Security Run Output Message-ID: <bda8d0b5-955c-4a6f-bd5b-49c0721640c3@app.fastmail.com> In-Reply-To: <20230326081128.00005b98@seibercom.net> References: <20230326081128.00005b98@seibercom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 26 Mar 2023, at 12:11, Gerard E. Seibert wrote:
> For quite some time now, I have been receiving a warning message of
> 1025 packages with mismatched checksums in the daily "Security Run
> Output" email. They are all prefixed with "py39-"
>
> I don't want to wast time posting the entire list here, but it is
> available upon request if someone wants it. My question is, how do I
> correct this problem? This is a FreeBSD 13.1-release-p7 machine.
>
> Thanks
Stuff like this:
binwalk-2.3.3: checksum mismatch for /usr/local/lib/python3.9/site-packages/binwalk/plugins/__pycache__/lzmavalid.cpython-39.opt-1.pyc
the patch that introduced this has since been reverted, so any new
or updated packages will sort themselves out after pkg upgrade.
https://reviews.freebsd.org/D34739
To fix any leftovers, just force-reinstall the affected packages:
pkg install -r FreeBSD -f <pkg_names>
I am not sure if this would preserve the flag that marks
packages as auto-installed, for example as a dependency of
another package.
You could do `pkg list prime-origins` before and after to compare
that. Using `pkg install --automatic` would set that flag, there
might be a smarter way to do that without actually reinstalling.
A+
Dave
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bda8d0b5-955c-4a6f-bd5b-49c0721640c3>