Date: Tue, 02 Dec 2025 21:07:33 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> To: Odhiambo Washington <odhiambo@gmail.com> Cc: The Doctor <doctor@doctor.nl2k.ab.ca>, questions <questions@freebsd.org> Subject: Re: FreeBSD 15.0-RELEASE: Trouble after upgrade Message-ID: <865xaohcl6.fsf@ltc.des.dev> In-Reply-To: <CAAdA2WMM4kuHRYFJxAZfme4GEiG_UM6tNS7jegFbu9Xb%2BRiJgA@mail.gmail.com> (Odhiambo Washington's message of "Tue, 2 Dec 2025 20:03:26 %2B0300") References: <CAAdA2WMtqWL-KPW8smzVqQu5OgCUAHZ2wU5gmFOPpHAtq9jZOQ@mail.gmail.com> <aS8EyaCu_ooAAww_@doctor.nl2k.ab.ca> <86ikeohnn1.fsf@ltc.des.dev> <CAAdA2WMM4kuHRYFJxAZfme4GEiG_UM6tNS7jegFbu9Xb%2BRiJgA@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
Odhiambo Washington <odhiambo@gmail.com> writes:
> On Nov 26, there was an advisory ' FreeBSD Security Advisory
> FreeBSD-SA-25:10.unbound'. On that date I did the freebsd-update
> fetch && freebsd-update install thing. Today, I assumed that I was
> still updated. So it's obviously my mistake that I did not repeat the
> same thing today before upgrading to 15.0-REL.
No, if you updated on Nov 26 then you should have been fine, so
something else went wrong. I will try to see if I can reproduce it.
> Also ran the command, but I don't understand the meaning of the
> output:
None of these are particularly concerning. They are telling you that
you have modified configuration files (which is normal) and that some
files and directories have incorrect permissions (which is something
that sometimes happens with freebsd-update and isn't a big deal). There
are discrepancies in /usr/src but that's easily fixed by replacing the
entire source tree (rm -rf /usr/src then download and extract src.txz).
You can fix at least some of these issues by running the following
commands as root:
mtree -deU -p / -f /etc/mtree/BSD.root.dist
mtree -deU -p /var -f /etc/mtree/BSD.var.dist
mtree -deU -p /usr -f /etc/mtree/BSD.usr.dist
The only lines that surprise me are these:
/usr/lib/debug/usr/lib/libdevinfo.so.7.debug has SHA256 hash d06d59e4913a6103771409c598945e81dbaac857ea11271e2c03c92cd581aeef, but should have SHA256 hash 7653ff2946527fbb764e1932d767e4787fe8814c645f8c2d2359b43d0884f289.
/usr/lib/libdevinfo.a has SHA256 hash 378b792d00971a8d5ffc45ad7882d08190a244b97de5514f5b2eb75ea0f6db47, but should have SHA256 hash 3d412bd84e6a1a9914610c8e838e4c4afe3b131789d5e36e9371bd5de03e0d68.
/usr/lib/libdevinfo.so.7 has SHA256 hash 667f9592ed95a538077f3fc22461ed3d6ece3deae27b66ec1e6a271807f25110, but should have SHA256 hash 0f1f789aa07dbfdc1df637be1d31f41616ec74188c683d9f706bae0ceb61d904.
which is not critical and can be fixed by extracting those files from
base.txz as explained in my previous email.
I assume you will be switching to pkgbase at some point, which will make
correcting this kind of issue much easier.
DES
--
Dag-Erling Smørgrav - des@FreeBSD.org
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?865xaohcl6.fsf>