On 12/2/2025 11:11 AM, Matthew Seaman wrote:
On 02/12/2025 14:53, Darren Henderson wrote:
happens if you look under FreeBSD:15:aarch64. Again maybe that is
because
15-RELEASE-p0 doesn't exist yet?
It does, as of this morning. Although it's just '15.0-RELEASE' until
the first patch sets happen.
The directory exists but it's not accessible (via browser at least).
Going to https://pkg.freebsd.org/FreeBSD:15:amd64/base_release_0/ drops
you at
https://cloudfront.aws.pkgbase.freebsd.org/FreeBSD:15:amd64/base_release_0/
with an "AccessDenied" error. CDN issue?
Where as going to
https://pkg.freebsd.org/FreeBSD:14:amd64/base_release_0/ presents the
expected results.
The RE team has stated that there will be different pkg signing keys
for each OS major version or branch, so you'll need to look up the
appropriate keys for the version you want to upgrade to and add them
to your pkg.conf. I don't think there's a resource I could point you
to documenting all that (yet) but you can pull the information out of
git. Eg. these are the keys used for 15.0-RELEASE packages:
https://github.com/freebsd/freebsd-src/tree/release/15.0.0/share/keys/pkgbase-15/trusted
I was able to pull the pkgbase-15 sub from a 16.0-CURRENT system
(checked and they are the same as the ones on github) and that seems to
have done it.
Pulling in the pkgbase-15 sub and putting the following in
/usr/local/etc/pkg/repos/FreeBSD-base.conf:
/FreeBSD-base: {
url: "pkg+https://pkg.FreeBSD.org/${ABI}/base_release_0";,
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkgbase-15",
enabled: yes
}
/
And running:
/env ABI=FreeBSD:15:amd64 OSVERSION=1500000 pkg-static upgrade/
Successfully got the system to 15-RELEASE
It's interesting to note that FreeBSD-base.conf in 16-CURRENT still
points to general key - maybe when they get closer they will add a
pkgbase-16 key.
