Document?: How does one upgrade a poudriere-devel METHOD pkgbase 14.2-RELEASE-p? jail to be a 14.3-RELEASE based one?

The below forward is because I'd not confirmed my freebsd-doc subscription and so the send bounced.

The wording includes notes about poudriere(-devel) documentation problems of differences when pkgbase is involved as part of the more overall text about upgrading pkgbase 14.2 jails ot pkgbase 14.3 jails.


Begin forwarded message:

From: Mark Millard <marklmi@yahoo.com>
Subject: How does one upgrade a poudriere-devel METHOD pkgbase 14.2-RELEASE-p? jail to be a 14.3-RELEASE based one?
Date: June 6, 2025 at 21:42:16 PDT
To: FreeBSD-pkgbase@freebsd.org, FreeBSD Mailing List <freebsd-ports@freebsd.org>, Baptiste Daroussin <bapt@FreeBSD.org>, Bryan Drewery <bdrewery@FreeBSD.org>
Cc: freebsd-doc@freebsd.org

Given:

# poudriere jail -l
JAILNAME         VERSION         OSVERSION ARCH          METHOD  TIMESTAMP           PATH
release-aarch64  14.2-RELEASE-p1           aarch64       pkgbase 2025-06-06 21:19:04 /usr/local/poudriere/jails/release-aarch64

NOTE: updates within 14.2-RELEASE-p* did not change the VERSION text.

How does on get to the status:

release-aarch64  14.3-RELEASE              aarch64       pkgbase ???time??? /usr/local/poudriere/jails/release-aarch64

Is delete-and-recreate the intended technique?

Part of the issue here is variability that is not well documented: compare/contrast jail creation commands (just an example, not tied to the 14.2 -> 14.3 details):

poudriere jail -c -jmain-CA7   -aarm.armv7 -m null -M /usr/obj/DESTDIRs/main-CA7-poud -S /usr/main-src -v 15.0-CURRENT

vs.  for -mpkgbase=. . . being involved:

poudriere jail -c -jmain-armv7 -aarmv7     -U https://pkg.freebsd.org -mpkgbase=base_latest            -v 15

Note the -v difference and the -a difference.


Should "poudriere jail -u" for the 14.2 -> 14.3 update need:

-U https://pkg.freebsd.org
-mpkgbase=base_release_3
-v 14

Something else?



===
Mark Millard
marklmi at yahoo.com