Re: PKGBASE upgrade from ALPHAxx to BETAxx

On Oct 16, 2025, at 11:55, Mark Millard <marklmi@yahoo.com> wrote:

> On Oct 16, 2025, at 11:04, Colin Percival <cperciva@tarsnap.com> wrote:
> 
>> On 10/16/25 10:49, Patrick M. Hausen wrote:
>>>> Am 16.10.2025 um 19:44 schrieb Mark Millard <marklmi@yahoo.com>:
>>>> To my knowledge, /etc/pkg/ only has files that are expected to
>>>> apply to all systems, no matter how installed/updated. Also,
>>>> the files in /etc/pkg/ are expected to not be edited. The
>>>> overriding text goes in files in /usr/local/etc/pkg/respos/
>>>> instead. (Technically such are conventions, not requirements,
>>>> but they fit with FreeBSD update processes in a particular way.)
>>> I follow that argument.
>>> But isn't pkgbase supposed to be the new normal starting with 15.0?
>>> Sorry for the noise if I confused that. Then it will land in /etc/pkg/FreeBSD.conf in 16?
>> 
>> I'm planning on putting a "FreeBSD-base" repository configuration into
>> /etc/pkg/FreeBSD.conf in 15.
>> . . .
>> It will be disabled by default, in order
>> to avoid "pkg delete -af" problems, but "pkg upgrade -r FreeBSD-base"
>> should work out of the box.
> 
> Had I known such, various of my testing activities would
> have been different.
> 
> Looks like commands that handle the explicit reference to
> a disabled repository are documented as including:
> 
> /usr/local/share/man/man8/pkg-install.8.gz:                Install packages from only the named repository, irrespective
> /usr/local/share/man/man8/pkg-rquery.8.gz:             irrespective of the configured “enabled” status from repo.conf.
> /usr/local/share/man/man8/pkg-search.8.gz:                 irrespective of the configured “enabled” status from
> /usr/local/share/man/man8/pkg-update.8.gz:            update only the named repository, irrespective of the configured
> /usr/local/share/man/man8/pkg-upgrade.8.gz:                 Install packages from only the named repository, irrespective
> /usr/local/share/man/man8/pkg-version.8.gz:                 the named repository only, irrespective of the configured
> 
> Later I'll do some exploration of that.
> 
> I'll note that "man pkg-fetch" does not say that it does such:
> 
>     -r reponame, --repository reponame
>                   Fetches packages from the given reponame if multiple repo
>                   support is enabled.  See pkg.conf(5).
> 
>> The reasons this hasn't happened yet have to do with release engineering
>> processes and setting up the systems for building updates securely.

rquery, search, and version to not manipulate the
sets of base or port packages, so testing those
but being will to use "pkg update" . . .

Hmm. "pkg rquery" and "pkg search" and "pkg version"
do not seem to work as described. The context here is
a USB media with an armv7 snapshot image based temporary
system, not something that is (yet?) a pkgbase'd 
nstallation. I added the disabled FreeBSD-base and have
a enabled local port-package repository.

https://pkg.freebsd.org/FreeBSD:16:armv7/base_latest/

is populated, as is base_weekly/ . But latest/ and
quarterly/ and the rest are not yet.

# uname -apKU
FreeBSD RPi2Bv1p1 16.0-CURRENT FreeBSD 16.0-CURRENT #0 main-n281019-0dc634d48fcc: Fri Oct 10 00:15:55 UTC 2025     root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm.armv7/sys/GENERIC arm armv7 1600001 1600001

# pkg repos -e
pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
main-armv7-default: { 
    url             : "file:///usr/local/poudriere/data/packages/main-armv7-default",
    enabled         : yes,
    priority        : 0
  }

# pkg repos -d
pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
FreeBSD-base: { 
    url             : "pkg+http://pkg.FreeBSD.org/FreeBSD:16:armv7/base_latest",
    enabled         : no,
    priority        : 0,
    mirror_type     : "SRV",
    signature_type  : "FINGERPRINTS",
    fingerprints    : "/usr/share/keys/pkg"
  }

# whoami
root


# pkg rquery -r FreeBSD-base %n-%v FreeBSD-src
pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
pkg: Repository FreeBSD-base cannot be opened. 'pkg update' required

# pkg update -r FreeBSD-base
pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
Updating FreeBSD-base repository catalogue...
FreeBSD-base is up to date.

# pkg rquery -r FreeBSD-base %n-%v FreeBSD-src
pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
pkg: Repository FreeBSD-base cannot be opened. 'pkg update' required

# pkg search -r FreeBSD-base FreeBSD-src
pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
pkg: Repository FreeBSD-base cannot be opened. 'pkg update' required

# pkg version -r FreeBSD-base -n FreeBSD-src
pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
Updating FreeBSD-base repository catalogue...
FreeBSD-base is up to date.
pkg: Repository FreeBSD-base cannot be opened. 'pkg update' required


But, for example, . . .

# man pkg-rquery
PKG-RQUERY(8)           FreeBSD System Manager's Manual          PKG-RQUERY(8)

NAME
     pkg rquery – query information from remote repositories

SYNOPSIS
     pkg rquery -I|query-format pkg-name
     pkg rquery [-aU] [-r reponame] -I|query-format
     pkg rquery [-U] [-Cgix] [-e evaluation-condition] [-r reponame]
                -I|query-format pattern ...

. . .

OPTIONS
     The following options are supported by pkg rquery:

     . . .

     -r reponame, --repository reponame
             Query for data about packages from only the named repository,
             irrespective of the configured “enabled” status from repo.conf.
             By default, catalogues for all enabled repositories are queried.

     . . .



So, the above behavior is not obvious to me from
the documentation.


===
Mark Millard
marklmi at yahoo.com