Date: Tue, 16 Dec 2025 19:25:10 -0800 From: Colin Percival <cperciva@freebsd.org> To: freebsd-security@freebsd.org, freebsd-pkgbase@FreeBSD.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-25:12.rtsold Message-ID: <3f5c61f2-b3ae-4a95-b22a-659b4fa9c0a6@freebsd.org> In-Reply-To: <20251217010214.E6507E38F@freefall.freebsd.org>
index | next in thread | previous in thread | raw e-mail
On 12/16/25 17:02, FreeBSD Security Advisories wrote: > This issue is corrected as of the corresponding Git commit hash in the > following stable and release branches: > > Branch/path Hash Revision > ------------------------------------------------------------------------- > releng/15.0/ 408f5c61821f releng/15.0-n280998 A quick heads-up here for pkgbase users: If you upgrade to 15.0-RELEASE-p1 and run `uname -v` you will see a different hash from this. This is due to a glitch in the way we build security updates for pkgbase -- in order to make sure that we have updated packages ready to go when commits go into the src tree, we build them in advance by taking the src tree from the release and applying patches generated with `git format-patch` from the security team's staging tree; but it turns out that running `git am` and ending up with the exact same commit hashes is not trivial. I'm hoping to get this sorted out before 15.0-RELEASE-p2! -- Colin Percival FreeBSD Release Engineering Lead & EC2 platform maintainer Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoidhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3f5c61f2-b3ae-4a95-b22a-659b4fa9c0a6>