On Jun 7, 2025, at 00:03, Dag-Erling Smørgrav <[email protected]> wrote:
> Mark Millard <[email protected]> writes: >> # poudriere jail -c -jrelease-aarch64 -aaarch64 -U >> https://pkg.freebsd.org -mpkgbase=base_release_3 -v 14 -X > > How do you expect poudriere to interpret `-v 14`? > -v 14.3-RELEASE does not work for -mpkgbase= usage. The -v VERSION_HERE is substituted into the text for: https://pkg.freebsd.org/FreeBSD:VERSION_HERE:aarch64/ (aarch64 example) The only paths that work have one of: 14 15 (for now). For reference: # poudriere jail -c -jMYTEST -U https://pkg.freebsd.org -mpkgbase=base_release_3 -v 14.3-RELEASE -X [00:00:00] Creating MYTEST fs at /usr/local/poudriere/jails/MYTEST... done [00:00:00] Installing 14.3-RELEASE amd64 from https://pkg.freebsd.org ...pkg: Invalid version in ABI string 'FreeBSD:14.3-RELEASE:amd64' pkg: Cannot parse configuration file! pkg: Invalid version in ABI string 'FreeBSD:14.3-RELEASE:amd64' pkg: Cannot parse configuration file! pkg: Invalid version in ABI string 'FreeBSD:14.3-RELEASE:amd64' pkg: Cannot parse configuration file! [00:00:00] Recording filesystem state for clean... done [00:00:00] Jail MYTEST 14.3-RELEASE amd64 is ready to be used # poudriere jail -c -jMYTEST -U https://pkg.freebsd.org -mpkgbase=base_release_3 -v 14.3 -X [00:00:00] Creating MYTEST fs at /usr/local/poudriere/jails/MYTEST... done [00:00:00] Installing 14.3 amd64 from https://pkg.freebsd.org ...pkg: Invalid version in ABI string 'FreeBSD:14.3:amd64' pkg: Cannot parse configuration file! pkg: Invalid version in ABI string 'FreeBSD:14.3:amd64' pkg: Cannot parse configuration file! pkg: Invalid version in ABI string 'FreeBSD:14.3:amd64' pkg: Cannot parse configuration file! [00:00:00] Recording filesystem state for clean... done [00:00:00] Jail MYTEST 14.3 amd64 is ready to be used Technically the information is encoded in the 3 of: base_release_3 so "14.3" could be built. This is messy also because -m??? for it not being -mpkgbase do use the notation: -v 14.3-RELEASE -aARCH for -mpkgbase= also does not match what is used for other -m??? alternatives. In this case, for -mpkgbase= the -aARCH has ARCH directly substituted into https://pkg.freebsd.org/FreeBSD:VERSION_HERE:ARCH/ and the normal TARGET.TARGET_ARCH does not work --but does for other -m??? alternatives. Nor does -aarm64 work instead of -aarch64 (for example). === Mark Millard marklmi at yahoo.com
