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 paranoid
