Date: Tue, 3 Sep 2024 16:35:21 -0800 From: Gary Aitken <freebsd@dreamchaser.org> To: ax disroo <ax61@disroot.org> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: packages with mismatched checksums Message-ID: <310a6f63-88fc-4906-8599-6048947a9f59@dreamchaser.org> In-Reply-To: <B82B2723-CD7D-4E7E-B84C-6E21C63ADB1D@disroot.org> References: <ba51bc15-51dd-4993-871b-fc47c8da366b@dreamchaser.org> <B82B2723-CD7D-4E7E-B84C-6E21C63ADB1D@disroot.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/2/24 13:05, ax disroo wrote: >> On Sep 1, 2024, at 6:19 AM, Gary Aitken wrote: >> >> What is the right way to fix / check a package reported as having >> a mismatched checksum, assuming it hasn't been modified? > > Try pkg-check(8) > https://man.freebsd.org/cgi/man.cgi?query=pkg-check&apropos=0&sektion=8&manpath=FreeBSD+14.1-RELEASE+and+Ports&arch=default&format=html ...> Check check … # pkg check --checksums --dependencies --dry-run --all > --verbose that reports the problem, but doesn't resolve it. > Update … # pkg check --recompute --dependencies --shlibs --all according to the man page --recompute should only be used when one has modified the package. AFIK I haven't touched it, so this would not be wise. So the original question still open: what's the right way to fix this? Reinstall the package using pkg install -f foo ? Gary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?310a6f63-88fc-4906-8599-6048947a9f59>
