Re: pkgbase upgrade from 14.3-RELEASE-p6 to 15.0-RELEASE

From: Matthew Seaman <matthew_at_FreeBSD.org>
Date: Tue, 02 Dec 2025 16:11:53 UTC
On 02/12/2025 14:53, Darren Henderson wrote:
> I'm missing something...
> 
> On a basified 14.3-RELEASE-p6 system  I end up seeing a pkg error relating
> to not being able to find a trusted key but the needed keys are there and
> readable. This is pointing at base_relase_0 (and maybe that's the problem?
> Do we start counting at 0 for the initial release?) using an ABI of
> FreeBSD:15:amd64
> 
> The problem appears to be related to an issue evident on pkg.frrebsd.org.
> If you go to https://pkg.freebsd.org/, click on FreeBSD:15:amd64 and then
> click on base_release_0 you get an error message of "AccessDenied". Also a
> message about XML file does not appear to have style information. The same
> 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.

> I can move from 14.3-RELEASE-p6 to 15.0-STABLE just fine if I use  url:
> "pkg+https://pkg.FreeBSD.org/${ABI}/base_latest" but I'm not seeing how to
> get from 14.3-RELEASE-p6 to 15-RELEASE.
> 
> Apologies if I'm missing something basic here.

Upgrades accrose different major versions or between -STABLE and 
-RELEASE streams are all conceptually the same with pkgbase

    * Set up pkg.conf to use packages from the OS version you want,
      typically involving overriding '${ABI}' in pkg URLs and
      ${OSVERSION}.

    * Do a `pkg upgrade` possibly involving several stages of upgrading
      different classes of software -- kernel vs. vital shared OS
      components like libraries vs. end user software packages and
      possibly in several steps via intermediate versions.

That's the high level description.  Normally you'ld break that second 
step down into smaller pieces with levels of testing between each so you 
could perform the upgrade confident of your system still working or 
decide to abort and back-out in the middle without having to exercise 
the nuclear option of recovering from backup.  For me, that boils down 
to 'create a new boot environment, boot into the new BE; if it doesn't 
work, revert to the original BE and think again.'

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

	Cheers,

	Matthew