From Newsgroup: muc.lists.freebsd.stable

Hello Stable Gang,
I took a leap into PKGBASE , I installed 15-ALPHA5 from a usb and selected pkgbase . It works. So i see that BETA1 is out and i am stumped what should we do to upgrade from ALPHA to BETA vi pkg ?
I will leave it there , thanks again.
---
Mark Saad | nonesuch@longcount.org--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

Hi!

I took a leap into PKGBASE , I installed 15-ALPHA5 from a usb and selected pkgbase . It works. So i see that BETA1 is out and i am stumped what should we do to upgrade from ALPHA to BETA vi pkg ?

I did this:

cd /usr/local/etc/pkg/repos
vi 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/pkg",
enabled: yes
}
-----------

Then:

pkg update
pkg upgrade

This worked from ALPHA5.
--
pi@FreeBSD.org +49 171 3101372 Now what ?


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

That's likely not enough; check your config settings for packages
derived from the ports tree.
Using latest on releng/15, such as 15.0-BETA1, verify:
FreeBSD-ports: {
url: "pkg+https://pkg.FreeBSD.org/${ABI}/latest",
enabled: yes,
priority: 0,
mirror_type: "SRV",
signature_type: "FINGERPRINTS",
fingerprints: "/usr/share/keys/pkg"
}
FreeBSD-ports-kmods: {
url:
"pkg+https://pkg.FreeBSD.org/${ABI}/kmods_latest_${VERSION_MINOR}",
enabled: yes,
priority: 0,
mirror_type: "SRV",
signature_type: "FINGERPRINTS",
fingerprints: "/usr/share/keys/pkg"
}
Substitute latest by quarterly accordingly, if so desired.
You may need to use -f to force (re)installation of packages that were
version tagged with '1500500' as installed from a repository
where its packages were built against ALPHA5; otherwise these won't get updated.
According to the Handbook, for the FreeBSD-base repository you can use:
url: "pkg+https://pkg.FreeBSD.org/${ABI}/base_release_${VERSION_MINOR}",
Eric
On Thu, Oct 16, 2025 at 2:02rC>PM Kurt Jaeger <pi@freebsd.org> wrote:

Hi!

I took a leap into PKGBASE , I installed 15-ALPHA5 from a usb and selected pkgbase . It works. So i see that BETA1 is out and i am stumped what should we do to upgrade from ALPHA to BETA vi pkg ?

I did this:

cd /usr/local/etc/pkg/repos
vi 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/pkg",
enabled: yes
}
-----------

Then:

pkg update
pkg upgrade

This worked from ALPHA5.

--
pi@FreeBSD.org +49 171 3101372 Now what ?

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

Hi!

That's likely not enough; check your config settings for packages
derived from the ports tree.

Yes, sorry. I build my own ports, so use my repo for the packages.
--
pi@FreeBSD.org +49 171 3101372 Now what ?


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

On 2025-10-16 15:33, Patrick M. Hausen wrote:

Hi all,

Am 16.10.2025 um 14:02 schrieb Kurt Jaeger <pi@freebsd.org>:

I did this:

cd /usr/local/etc/pkg/repos
vi 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/pkg",
enabled: yes
}
-----------

Why is the repository configuration for the packaged *base* system in /usr/*local*/etc?

Because pkg(8) is not in base but from ports.
Overriding base FreeBSD-base repository config with a config file
located in LOCALPREFIX:-/usr/local is comprehensible and the way users
are supposed to do according to the notes in /etc/pkg/FreeBSD.conf.


best,

-harry



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

On 2025-10-16 19:04, Patrick M. Hausen wrote:

Hi,

Am 16.10.2025 um 18:58 schrieb Harry Schmalzbauer <freebsd@omnilan.de>:
Overriding base FreeBSD-base repository config with a config file located in LOCALPREFIX:-/usr/local is comprehensible and the way users are supposed to do according to the notes in /etc/pkg/FreeBSD.conf.

Overriding - granted. I have been doing the same for years.

But on a fresh FreeBSD 15 pkgbase system the repos for
FreeBSD-ports and FreeBSD-ports-kmods are configured in
/etc/pkg and the repo for FreeBSD-base itself in /usr/local/etc/pkg/repos.

Or to put it differently:

Why does /etc/pkg/FreeBSD.conf *not* contain the repo for packaged base?

I think that's odd.

It is, otoh. we're on Alpha/Beta...
I guess this will change.
In a recent Reply Collins noted that the package signing infrastructure
for the base repository wasn't ready... so for the release, some more
things will change. Just a wild guess though...

Best,
-harry




--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

Patrick M. Hausen <hausen_at_punkt.de> wrote on
Date: Thu, 16 Oct 2025 17:04:37 UTC :
(First I quote some missing context for reference:)
QUOTE

Am 16.10.2025 um 14:02 schrieb Kurt Jaeger <pi@freebsd.org>:

I did this:

cd /usr/local/etc/pkg/repos
vi 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/pkg",
enabled: yes
}
-----------

END QUOTE

Hi,

Am 16.10.2025 um 18:58 schrieb Harry Schmalzbauer <freebsd@omnilan.de>: Overriding base FreeBSD-base repository config with a config file located in LOCALPREFIX:-/usr/local is comprehensible and the way users are supposed to do according to the notes in /etc/pkg/FreeBSD.conf.

Overriding - granted. I have been doing the same for years.

But on a fresh FreeBSD 15 pkgbase system the repos for
FreeBSD-ports and FreeBSD-ports-kmods are configured in
/etc/pkg and the repo for FreeBSD-base itself in /usr/local/etc/pkg/repos.

Or to put it differently:

Why does /etc/pkg/FreeBSD.conf *not* contain the repo for packaged base?

I think that's odd.

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.)
It is only appropriate to have FreeBSD-base defined in an enabled
state if one is using pkgbase instead of freebsd-update or source
based: otherwise pkg might do inappropriate things with the base
packages. pkgbase is not the default (yet) and also is not the
only option (ever).
It could be viewed as odder to have a /etc/pkg/ file with a
definition that was disabled:
FreeBSD-base: {
url: "pkg+https://pkg.FreeBSD.org/${ABI}/base_release_0",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: no
}
and then, for pkgbase systems, a manually created/adjusted file
in /usr/local/etc/pkg/respos/ that has the:
FreeBSD-base: { enabled: yes }
Even when disabled, if defined FreeBSD-base could potentially
be referenced on the pkg command line with -rFreeBSD-base
specifying the repository to use and some commands. For
example "man pkg-install" reports:
-r reponame, --repository reponame
Install packages from only the named repository, irrespective
of the configured rCLenabledrCY status from repo.conf.
But, absent a definition, that notation could not find base
packages, avoiding a form of potential foot-shooting.
Note: My memory is that some documented "irrespective" notes
for -r reponame do not all match the actual behavior for the
command that makes the claim.
===
Mark Millard
marklmi at yahoo.com
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

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.

The reasons this hasn't happened yet have to do with release engineering processes and setting up the systems for building updates securely.
--
Colin Percival
FreeBSD Release Engineering Lead & EC2 platform maintainer
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

On Oct 16, 2025, at 10:49, Patrick M. Hausen <hausen@punkt.de> wrote:

Hi,

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?

No. https://lists.freebsd.org/archives/dev-commits-src-branches/2025-October/024436.html
reports that the auto option of bsdinstall has been changed as follows to indicate
"technology preview":
diff --git a/usr.sbin/bsdinstall/scripts/auto b/usr.sbin/bsdinstall/scripts/auto
index 61d52065af2a..8058b1a41dbf 100755
--- a/usr.sbin/bsdinstall/scripts/auto
+++ b/usr.sbin/bsdinstall/scripts/auto
@@ -209,9 +209,9 @@ if [ ! -f $BSDINSTALL_DISTDIR/MANIFEST ]; then
PKGBASE=yes
else
bsddialog --backtitle "$OSNAME Installer" --title "Select Installation Type" \
- --yes-label "Traditional" --no-label "Packages (Experimental)" --yesno \
+ --yes-label "Distribution Sets" --no-label "Packages (Tech Preview)" --yesno \
$PKGBASE_DEFAULT_BUTTON \
- "Would you like to install the base system using traditional distribution sets or packages (experimental)?" 0 0
+ "Would you like to install the base system using traditional distribution sets or packages (technology preview)?" 0 0
if [ $? -eq 1 ]; then
PKGBASE=yes
fi
Similarly its jail option has been changed to also indicate that:
diff --git a/usr.sbin/bsdinstall/scripts/jail b/usr.sbin/bsdinstall/scripts/jail
index f2c7ef2b37de..3b1b2ee98fff 100755
--- a/usr.sbin/bsdinstall/scripts/jail
+++ b/usr.sbin/bsdinstall/scripts/jail
@@ -175,8 +175,8 @@ fi

if [ ! "$nonInteractive" == "YES" ]; then
bsddialog --backtitle "$OSNAME Installer" --title "Select Installation Type" \
- --yes-label "Traditional" --no-label "Packages (Experimental)" --yesno \
- "Would you like to install the base system using traditional distribution sets or packages (experimental)?" 0 0
+ --yes-label "Distribution Sets" --no-label "Packages (Tech Preview)" --yesno \
+ "Would you like to install the base system using traditional distribution sets or packages (technology preview)?" 0 0
if [ $? -eq 1 ]; then
PKGBASE=yes
fi

Sorry for the noise if I confused that.

Keeping up with the expected status of such is not easy
and it is a fairly recent change.

Then it will land in /etc/pkg/FreeBSD.conf in 16?

Answering now for events years in the future is likely
to have a conditional status. Also, even if "traditional
distribution sets" are removed in 16, there would still
be the types of issues for source installs and updates
vs. pkgbase ones.
Prior to pkgbase, this was an area with no distinctions
to be made for /etc/pkg/ and /usr/local/etc/pkg/repos/ .
===
Mark Millard
marklmi at yahoo.com
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

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.

Even for installs via "traditional distribution sets"? Or just for
"technology preview" installs?

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 rCLenabledrCY status from repo.conf.
/usr/local/share/man/man8/pkg-search.8.gz: irrespective of the configured rCLenabledrCY 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.

===
Mark Millard
marklmi at yahoo.com
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

On 10/16/25 11:55, Mark Millard 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.

Even for installs via "traditional distribution sets"? Or just for "technology preview" installs?

Yes. Having the repository definition there is harmless, and we don't
want to deal with the chaos of people having different versions of that
file depending on how they installed the OS.
--
Colin Percival
FreeBSD Release Engineering Lead & EC2 platform maintainer
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable


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 rCLenabledrCY status from repo.conf.
/usr/local/share/man/man8/pkg-search.8.gz: irrespective of the configured rCLenabledrCY 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 rCo 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 rCLenabledrCY 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
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

I cannot reproduce your behaviour on my BETA1.
What pkg are you running?
As a comparison, on 15-BETA1 (amd64, pkgbasified), all seems as
expected; see below.
Eric
[0-0] # date -u; uname -apKU; pkg -v
Fri Oct 17 09:45:53 UTC 2025
FreeBSD q210 15.0-BETA1 FreeBSD 15.0-BETA1
releng/15.0-n280655-36a923a476dc GENERIC amd64 amd64 1500067 1500067
2.3.1
[1-0] # pkg repos -e -d
FreeBSD-ports: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/latest",
enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}
FreeBSD-ports-kmods: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/kmods_latest_0",
enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}
FreeBSD-base: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/base_release_0",
enabled : no,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}
[2-0] # pkg rquery -r FreeBSD-base '%R %o %n %v' FreeBSD-src
FreeBSD-base base/FreeBSD-src FreeBSD-src 15.0.b1.20251016034928
[3-0] # pkg update -r FreeBSD-base
Updating FreeBSD-base repository catalogue...
FreeBSD-base is up to date.
[4-0] # pkg rquery -r FreeBSD-base '%R %o %n %v' FreeBSD-src
FreeBSD-base base/FreeBSD-src FreeBSD-src 15.0.b1.20251016034928
[5-0] # pkg search -r FreeBSD-base FreeBSD-src FreeBSD-src-15.0.b1.20251016034928 System userland source code FreeBSD-src-sys-15.0.b1.20251015211959 System kernel source code
[6-0] # pkg version -r FreeBSD-base -n FreeBSD-src
Updating FreeBSD-base repository catalogue...
FreeBSD-base is up to date.
FreeBSD-src-15.0.b1.20251016034928 =
[7-0] #
----- Original Message -----
From: "Mark Millard" <marklmi@yahoo.com>
To: "Colin Percival" <cperciva@tarsnap.com>
Cc: "Patrick M. Hausen" <hausen@punkt.de>, "FreeBSD-STABLE Mailing
List" <freebsd-stable@freebsd.org>
Sent: Thursday, 16 October, 2025 23:16:53
Subject: 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 rCLenabledrCY status from repo.conf.
/usr/local/share/man/man8/pkg-search.8.gz: irrespective of the configured rCLenabledrCY 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 rCo 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 rCLenabledrCY 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
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

On Oct 17, 2025, at 03:24, Erichans <erichanskrs@gmail.com> wrote:

I cannot reproduce your behaviour on my BETA1.
What pkg are you running?

# pkg -v
2.3.1

As a comparison, on 15-BETA1 (amd64, pkgbasified),

Reminder: this report was for a non-pkgbasified context doing
operations that do not install/upgrade or the like, just
rquery, search, and version.
(I sent a separate notice to the lists for another oddity
for a pkgbase'd context and that got an independent
confirmation. Turns out that oddity also happened here.
More later below.)

all seems as
expected; see below.

In a different type of context than I tested and reported
on.

Eric

[0-0] # date -u; uname -apKU; pkg -v
Fri Oct 17 09:45:53 UTC 2025
FreeBSD q210 15.0-BETA1 FreeBSD 15.0-BETA1
releng/15.0-n280655-36a923a476dc GENERIC amd64 amd64 1500067 1500067
2.3.1
[1-0] # pkg repos -e -d
FreeBSD-ports: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/latest",
enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}

My context has a locally built ports repository
enabled (main-armv7-default), not FreeBSD-ports.
But FreeBSD-ports is explicitly disabled.
I do have packages from main-armv7-default installed,
including pkg itself:
# pkg info pkg
pkg: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended
pkg-2.3.1
Name : pkg
Version : 2.3.1
Installed on : Wed Oct 15 21:24:37 2025 PDT
Origin : ports-mgmt/pkg
Architecture : FreeBSD:16:armv7
Prefix : /usr/local
Categories : ports-mgmt
Licenses : BSD2CLAUSE
Maintainer : pkg@FreeBSD.org
WWW : https://github.com/freebsd/pkg
Comment : Package manager
Options :
DOCS : on
Shared Libs required:
libarchive.so.7
libc.so.7
libcrypto.so.35
libelf.so.2
libgcc_s.so.1
libjail.so.1
libm.so.5
libssl.so.35
libthr.so.3
libutil.so.10
libz.so.6
Shared Libs provided:
libpkg.so.4
Annotations :
FreeBSD_version: 1600000
build_timestamp: 2025-09-14T00:45:39+00:00
built_by : poudriere-git-3.4.99.20250724
port_checkout_unclean: no
port_git_hash : e8009782a2b6
ports_top_checkout_unclean: yes
ports_top_git_hash: 7e86a0d71167
repo_type : binary
repository : main-armv7-default
Flat size : 45.2MiB
Description :
Package management tool

FreeBSD-ports-kmods: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/kmods_latest_0",
enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}

My context has has nothing analogous to
FreeBSD-ports-kmods enabled but instead
explicitly disables it (and FreeBSD-ports):
# cat /etc/pkg/FreeBSD.conf
#
# To disable a repository, instead of modifying or removing this file,
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file, e.g.:
#
# mkdir -p /usr/local/etc/pkg/repos
# echo "FreeBSD-ports: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf
# echo "FreeBSD-ports-kmods: { enabled: no }" >> /usr/local/etc/pkg/repos/FreeBSD.conf
#
FreeBSD-base: {
url: "pkg+http://pkg.FreeBSD.org/${ABI}/base_latest",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: no
}
FreeBSD-ports: {
url: "pkg+https://pkg.FreeBSD.org/${ABI}/latest",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: yes
}
FreeBSD-ports-kmods: {
url: "pkg+https://pkg.FreeBSD.org/${ABI}/kmods_latest",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: yes
}
# cat /usr/local/etc/pkg/repos/FreeBSD.conf
#
# To disable a repository, instead of modifying or removing this file,
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file, e.g.:
#
# mkdir -p /usr/local/etc/pkg/repos
# echo "FreeBSD-ports: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf
# echo "FreeBSD-ports-kmods: { enabled: no }" >> /usr/local/etc/pkg/repos/FreeBSD.conf
#
#FreeBSD-base: { enabled: yes }
FreeBSD-ports: { enabled: no }
FreeBSD-ports-kmods: { enabled: no }
Noteably, "pkg repos" does not list the
FreeBSD-ports-kmods at all (as either -d or -e).
I preprduced this in a pkgbase context and is
what I reported separately for that context.
# cat /usr/local/etc/pkg/repos/main-armv7-default.conf
main-armv7-default: {
url: "file:///usr/local/poudriere/data/packages/main-armv7-default",
mirror_type: "none",
enabled: yes
}

FreeBSD-base: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/base_release_0",
enabled : no,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}

This one is analogous to what I reported, but I have
base_latest instead of base_release_0 .

[2-0] # pkg rquery -r FreeBSD-base '%R %o %n %v' FreeBSD-src
FreeBSD-base base/FreeBSD-src FreeBSD-src 15.0.b1.20251016034928
[3-0] # pkg update -r FreeBSD-base
Updating FreeBSD-base repository catalogue...
FreeBSD-base is up to date.
[4-0] # pkg rquery -r FreeBSD-base '%R %o %n %v' FreeBSD-src
FreeBSD-base base/FreeBSD-src FreeBSD-src 15.0.b1.20251016034928
[5-0] # pkg search -r FreeBSD-base FreeBSD-src FreeBSD-src-15.0.b1.20251016034928 System userland source code FreeBSD-src-sys-15.0.b1.20251015211959 System kernel source code
[6-0] # pkg version -r FreeBSD-base -n FreeBSD-src
Updating FreeBSD-base repository catalogue...
FreeBSD-base is up to date.
FreeBSD-src-15.0.b1.20251016034928 =
[7-0] #

----- Original Message -----
From: "Mark Millard" <marklmi@yahoo.com>
To: "Colin Percival" <cperciva@tarsnap.com>
Cc: "Patrick M. Hausen" <hausen@punkt.de>, "FreeBSD-STABLE Mailing
List" <freebsd-stable@freebsd.org>
Sent: Thursday, 16 October, 2025 23:16:53
Subject: 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 rCLenabledrCY status from repo.conf.
/usr/local/share/man/man8/pkg-search.8.gz: irrespective of the configured rCLenabledrCY 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.

Above is where I indicated that the context was
"not something that is (yet?) a pkgbase'd
[i]nstallation". (It is still not pkgbased.)

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 rCo 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 rCLenabledrCY 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
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

Thank you. You're running a normal pkg version, which is good to knowrCoit could
have been a development version, considering you're on FreeBSD 16.
I wasn't sure whether posting results from running -CURRENT on the
stable mailing list was intentional.
IrCOm aware there are substantial differences between your environment
and minerCoone being that you're running pkg on the armv7 architecture.
I'm not intimately familiar with all the differences between a packaged base and a conventional base.
Regarding 15.0-BETA1 and the oddity you mentioned, IrCOve encountered similar issuesrCosee PR 289216 and PR 289455rCoall on release versions. Things donrCOt seem
to have changed. For example, on my 15.0-BETA1 a disabled FreeBSD-ports-kmods repository is unexpectedly not printed by pkg repositories or similar
pkg -vv command,
which seems in line with your findings:
[0-0] % date -u; uname -apKU; pkg -v
Sat Oct 18 11:40:49 UTC 2025
FreeBSD q210 15.0-BETA1 FreeBSD 15.0-BETA1
releng/15.0-n280674-f6751f1fc5a9 GENERIC amd64 amd64 1500067 1500067
2.3.1
[1-0] % grep -h '^[^#].*' /usr/local/etc/pkg/repos/*conf
FreeBSD-ports: {
url: "pkg+https://pkg.FreeBSD.org/${ABI}/latest",
enabled: yes,
priority: 0,
mirror_type: "SRV",
signature_type: "FINGERPRINTS",
fingerprints: "/usr/share/keys/pkg"
}
FreeBSD-ports-kmods: {
url:
"pkg+https://pkg.FreeBSD.org/${ABI}/kmods_latest_${VERSION_MINOR}",
enabled: no,
priority: 0,
mirror_type: "SRV",
signature_type: "FINGERPRINTS",
fingerprints: "/usr/share/keys/pkg"
}
FreeBSD-base: {
url: "pkg+https://pkg.FreeBSD.org/${ABI}/base_release_${VERSION_MINOR}",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: yes
}
[2-0] % pkg -vv | sed -nE -e '/OSVERSION|ABI/ p' -e '/^Repositories:/,$ p' IGNORE_OSVERSION = true;
ABI = "FreeBSD:15:amd64";
ALTABI = "freebsd:15:x86:64";
OSVERSION = "1500067";
Repositories:
FreeBSD-ports: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/latest",
enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}
FreeBSD-base: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/base_release_0",
enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}
[3-0] % pkg repositories -d -e
FreeBSD-ports: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/latest",
enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}
FreeBSD-base: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/base_release_0",
enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}
[4-0] %
Eric
On Fri, Oct 17, 2025 at 3:17rC>PM Mark Millard <marklmi@yahoo.com> wrote:

On Oct 17, 2025, at 03:24, Erichans <erichanskrs@gmail.com> wrote:

I cannot reproduce your behaviour on my BETA1.
What pkg are you running?

# pkg -v
2.3.1

As a comparison, on 15-BETA1 (amd64, pkgbasified),

Reminder: this report was for a non-pkgbasified context doing
operations that do not install/upgrade or the like, just
rquery, search, and version.

(I sent a separate notice to the lists for another oddity
for a pkgbase'd context and that got an independent
confirmation. Turns out that oddity also happened here.
More later below.)

all seems as
expected; see below.

In a different type of context than I tested and reported
on.

Eric

[0-0] # date -u; uname -apKU; pkg -v
Fri Oct 17 09:45:53 UTC 2025
FreeBSD q210 15.0-BETA1 FreeBSD 15.0-BETA1
releng/15.0-n280655-36a923a476dc GENERIC amd64 amd64 1500067 1500067
2.3.1
[1-0] # pkg repos -e -d
FreeBSD-ports: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/latest",
enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}

My context has a locally built ports repository
enabled (main-armv7-default), not FreeBSD-ports.
But FreeBSD-ports is explicitly disabled.

I do have packages from main-armv7-default installed,
including pkg itself:

# pkg info pkg
pkg: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended
pkg-2.3.1
Name : pkg
Version : 2.3.1
Installed on : Wed Oct 15 21:24:37 2025 PDT
Origin : ports-mgmt/pkg
Architecture : FreeBSD:16:armv7
Prefix : /usr/local
Categories : ports-mgmt
Licenses : BSD2CLAUSE
Maintainer : pkg@FreeBSD.org
WWW : https://github.com/freebsd/pkg
Comment : Package manager
Options :
DOCS : on
Shared Libs required:
libarchive.so.7
libc.so.7
libcrypto.so.35
libelf.so.2
libgcc_s.so.1
libjail.so.1
libm.so.5
libssl.so.35
libthr.so.3
libutil.so.10
libz.so.6
Shared Libs provided:
libpkg.so.4
Annotations :
FreeBSD_version: 1600000
build_timestamp: 2025-09-14T00:45:39+00:00
built_by : poudriere-git-3.4.99.20250724
port_checkout_unclean: no
port_git_hash : e8009782a2b6
ports_top_checkout_unclean: yes
ports_top_git_hash: 7e86a0d71167
repo_type : binary
repository : main-armv7-default
Flat size : 45.2MiB
Description :
Package management tool

FreeBSD-ports-kmods: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/kmods_latest_0", enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}

My context has has nothing analogous to
FreeBSD-ports-kmods enabled but instead
explicitly disables it (and FreeBSD-ports):

# cat /etc/pkg/FreeBSD.conf
#
# To disable a repository, instead of modifying or removing this file,
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file, e.g.:
#
# mkdir -p /usr/local/etc/pkg/repos
# echo "FreeBSD-ports: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf
# echo "FreeBSD-ports-kmods: { enabled: no }" >> /usr/local/etc/pkg/repos/FreeBSD.conf
#

FreeBSD-base: {
url: "pkg+http://pkg.FreeBSD.org/${ABI}/base_latest",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: no
}

FreeBSD-ports: {
url: "pkg+https://pkg.FreeBSD.org/${ABI}/latest",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: yes
}
FreeBSD-ports-kmods: {
url: "pkg+https://pkg.FreeBSD.org/${ABI}/kmods_latest",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: yes
}

# cat /usr/local/etc/pkg/repos/FreeBSD.conf
#
# To disable a repository, instead of modifying or removing this file,
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file, e.g.:
#
# mkdir -p /usr/local/etc/pkg/repos
# echo "FreeBSD-ports: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf
# echo "FreeBSD-ports-kmods: { enabled: no }" >> /usr/local/etc/pkg/repos/FreeBSD.conf
#

#FreeBSD-base: { enabled: yes }
FreeBSD-ports: { enabled: no }
FreeBSD-ports-kmods: { enabled: no }

Noteably, "pkg repos" does not list the
FreeBSD-ports-kmods at all (as either -d or -e).
I preprduced this in a pkgbase context and is
what I reported separately for that context.

# cat /usr/local/etc/pkg/repos/main-armv7-default.conf
main-armv7-default: {
url: "file:///usr/local/poudriere/data/packages/main-armv7-default",
mirror_type: "none",
enabled: yes
}

FreeBSD-base: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/base_release_0", enabled : no,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}

This one is analogous to what I reported, but I have
base_latest instead of base_release_0 .

[2-0] # pkg rquery -r FreeBSD-base '%R %o %n %v' FreeBSD-src
FreeBSD-base base/FreeBSD-src FreeBSD-src 15.0.b1.20251016034928
[3-0] # pkg update -r FreeBSD-base
Updating FreeBSD-base repository catalogue...
FreeBSD-base is up to date.
[4-0] # pkg rquery -r FreeBSD-base '%R %o %n %v' FreeBSD-src
FreeBSD-base base/FreeBSD-src FreeBSD-src 15.0.b1.20251016034928
[5-0] # pkg search -r FreeBSD-base FreeBSD-src FreeBSD-src-15.0.b1.20251016034928 System userland source code FreeBSD-src-sys-15.0.b1.20251015211959 System kernel source code
[6-0] # pkg version -r FreeBSD-base -n FreeBSD-src
Updating FreeBSD-base repository catalogue...
FreeBSD-base is up to date.
FreeBSD-src-15.0.b1.20251016034928 =
[7-0] #

----- Original Message -----
From: "Mark Millard" <marklmi@yahoo.com>
To: "Colin Percival" <cperciva@tarsnap.com>
Cc: "Patrick M. Hausen" <hausen@punkt.de>, "FreeBSD-STABLE Mailing
List" <freebsd-stable@freebsd.org>
Sent: Thursday, 16 October, 2025 23:16:53
Subject: 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 rCLenabledrCY status from repo.conf.
/usr/local/share/man/man8/pkg-search.8.gz: irrespective of the configured rCLenabledrCY 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.

Above is where I indicated that the context was
"not something that is (yet?) a pkgbase'd
[i]nstallation". (It is still not pkgbased.)

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 rCo 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 rCLenabledrCY 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

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

On Oct 18, 2025, at 04:41, Erichans <erichanskrs@gmail.com> wrote:

Thank you. You're running a normal pkg version, which is good to knowrCoit could
have been a development version, considering you're on FreeBSD 16.
I wasn't sure whether posting results from running -CURRENT on the
stable mailing list was intentional.

At this point main 16 with kernel.GENERIC-NODEBUG and stable/15 are
not all that distinct.

IrCOm aware there are substantial differences between your environment
and minerCoone being that you're running pkg on the armv7 architecture.

I also have access to amd64 and aarch64 contexts. The armv7 context
in question is the only one not based on using an official-pkgbase'd install/upgrade-sequence: an *-arm-armv7-GENERICSD-*.img.xz instead,
not converted to pkgbase (yet?).
My other report that was for a pkgbase context was not for on the
armv7.

I'm not intimately familiar with all the differences between a packaged base and a conventional base.

Regarding 15.0-BETA1 and the oddity you mentioned, IrCOve encountered similar issuesrCosee PR 289216 and PR 289455rCoall on release versions.

So that is at least 3 folks that have reported
examples. (Graham Perrin made a confirmation reply
to one of my messages.)
These seem likely to be problems with the upstream
pkg instead of with FreeBSD pkg configuration files
used with the pkg port-package. That means that the
versions of pkg are more likely important than the
versions of FreeBSD.
So it looks like the information needs to go in: https://github.com/freebsd/pkg/issues
So far as I know, your bugzilla submittals are the
earliest reports with the earliest versions of
pkg noted. References to such should be part of
the notes in https://github.com/freebsd/pkg/issues .
[Supplying full URLs to what you reference: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289216 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289455
]
Looks like you report that the type of issue goes back to
at least pkg 2.2.1 --and continues in pkg 2.3.1 for you,
not just for me and Graham.

Things donrCOt seem
to have changed. For example, on my 15.0-BETA1 a disabled FreeBSD-ports-kmods repository is unexpectedly not printed by pkg repositories or similar
pkg -vv command,
which seems in line with your findings:

[0-0] % date -u; uname -apKU; pkg -v
Sat Oct 18 11:40:49 UTC 2025
FreeBSD q210 15.0-BETA1 FreeBSD 15.0-BETA1
releng/15.0-n280674-f6751f1fc5a9 GENERIC amd64 amd64 1500067 1500067
2.3.1
[1-0] % grep -h '^[^#].*' /usr/local/etc/pkg/repos/*conf
FreeBSD-ports: {
url: "pkg+https://pkg.FreeBSD.org/${ABI}/latest",
enabled: yes,
priority: 0,
mirror_type: "SRV",
signature_type: "FINGERPRINTS",
fingerprints: "/usr/share/keys/pkg"
}
FreeBSD-ports-kmods: {
url:
"pkg+https://pkg.FreeBSD.org/${ABI}/kmods_latest_${VERSION_MINOR}",
enabled: no,
priority: 0,
mirror_type: "SRV",
signature_type: "FINGERPRINTS",
fingerprints: "/usr/share/keys/pkg"
}
FreeBSD-base: {
url: "pkg+https://pkg.FreeBSD.org/${ABI}/base_release_${VERSION_MINOR}",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: yes
}
[2-0] % pkg -vv | sed -nE -e '/OSVERSION|ABI/ p' -e '/^Repositories:/,$ p' IGNORE_OSVERSION = true;
ABI = "FreeBSD:15:amd64";
ALTABI = "freebsd:15:x86:64";
OSVERSION = "1500067";
Repositories:
FreeBSD-ports: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/latest",
enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}
FreeBSD-base: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/base_release_0",
enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}
[3-0] % pkg repositories -d -e
FreeBSD-ports: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/latest",
enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}
FreeBSD-base: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/base_release_0",
enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}
[4-0] %

Eric

On Fri, Oct 17, 2025 at 3:17rC>PM Mark Millard <marklmi@yahoo.com> wrote:

On Oct 17, 2025, at 03:24, Erichans <erichanskrs@gmail.com> wrote:

I cannot reproduce your behaviour on my BETA1.
What pkg are you running?

# pkg -v
2.3.1

As a comparison, on 15-BETA1 (amd64, pkgbasified),

Reminder: this report was for a non-pkgbasified context doing
operations that do not install/upgrade or the like, just
rquery, search, and version.

(I sent a separate notice to the lists for another oddity
for a pkgbase'd context and that got an independent
confirmation. Turns out that oddity also happened here.
More later below.)

all seems as
expected; see below.

In a different type of context than I tested and reported
on.

Eric

[0-0] # date -u; uname -apKU; pkg -v
Fri Oct 17 09:45:53 UTC 2025
FreeBSD q210 15.0-BETA1 FreeBSD 15.0-BETA1
releng/15.0-n280655-36a923a476dc GENERIC amd64 amd64 1500067 1500067
2.3.1
[1-0] # pkg repos -e -d
FreeBSD-ports: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/latest",
enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}

My context has a locally built ports repository
enabled (main-armv7-default), not FreeBSD-ports.
But FreeBSD-ports is explicitly disabled.

I do have packages from main-armv7-default installed,
including pkg itself:

# pkg info pkg
pkg: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended
pkg-2.3.1
Name : pkg
Version : 2.3.1
Installed on : Wed Oct 15 21:24:37 2025 PDT
Origin : ports-mgmt/pkg
Architecture : FreeBSD:16:armv7
Prefix : /usr/local
Categories : ports-mgmt
Licenses : BSD2CLAUSE
Maintainer : pkg@FreeBSD.org
WWW : https://github.com/freebsd/pkg
Comment : Package manager
Options :
DOCS : on
Shared Libs required:
libarchive.so.7
libc.so.7
libcrypto.so.35
libelf.so.2
libgcc_s.so.1
libjail.so.1
libm.so.5
libssl.so.35
libthr.so.3
libutil.so.10
libz.so.6
Shared Libs provided:
libpkg.so.4
Annotations :
FreeBSD_version: 1600000
build_timestamp: 2025-09-14T00:45:39+00:00
built_by : poudriere-git-3.4.99.20250724
port_checkout_unclean: no
port_git_hash : e8009782a2b6
ports_top_checkout_unclean: yes
ports_top_git_hash: 7e86a0d71167
repo_type : binary
repository : main-armv7-default
Flat size : 45.2MiB
Description :
Package management tool

FreeBSD-ports-kmods: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/kmods_latest_0",
enabled : yes,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}

My context has has nothing analogous to
FreeBSD-ports-kmods enabled but instead
explicitly disables it (and FreeBSD-ports):

# cat /etc/pkg/FreeBSD.conf
#
# To disable a repository, instead of modifying or removing this file,
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file, e.g.:
#
# mkdir -p /usr/local/etc/pkg/repos
# echo "FreeBSD-ports: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf
# echo "FreeBSD-ports-kmods: { enabled: no }" >> /usr/local/etc/pkg/repos/FreeBSD.conf
#

FreeBSD-base: {
url: "pkg+http://pkg.FreeBSD.org/${ABI}/base_latest",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: no
}

FreeBSD-ports: {
url: "pkg+https://pkg.FreeBSD.org/${ABI}/latest",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: yes
}
FreeBSD-ports-kmods: {
url: "pkg+https://pkg.FreeBSD.org/${ABI}/kmods_latest",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: yes
}

# cat /usr/local/etc/pkg/repos/FreeBSD.conf
#
# To disable a repository, instead of modifying or removing this file,
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file, e.g.:
#
# mkdir -p /usr/local/etc/pkg/repos
# echo "FreeBSD-ports: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf
# echo "FreeBSD-ports-kmods: { enabled: no }" >> /usr/local/etc/pkg/repos/FreeBSD.conf
#

#FreeBSD-base: { enabled: yes }
FreeBSD-ports: { enabled: no }
FreeBSD-ports-kmods: { enabled: no }


Noteably, "pkg repos" does not list the
FreeBSD-ports-kmods at all (as either -d or -e).
I preprduced this in a pkgbase context and is
what I reported separately for that context.


# cat /usr/local/etc/pkg/repos/main-armv7-default.conf
main-armv7-default: {
url: "file:///usr/local/poudriere/data/packages/main-armv7-default",
mirror_type: "none",
enabled: yes
}

FreeBSD-base: {
url : "pkg+https://pkg.FreeBSD.org/FreeBSD:15:amd64/base_release_0",
enabled : no,
priority : 0,
mirror_type : "SRV",
signature_type : "FINGERPRINTS",
fingerprints : "/usr/share/keys/pkg"
}

This one is analogous to what I reported, but I have
base_latest instead of base_release_0 .

[2-0] # pkg rquery -r FreeBSD-base '%R %o %n %v' FreeBSD-src
FreeBSD-base base/FreeBSD-src FreeBSD-src 15.0.b1.20251016034928
[3-0] # pkg update -r FreeBSD-base
Updating FreeBSD-base repository catalogue...
FreeBSD-base is up to date.
[4-0] # pkg rquery -r FreeBSD-base '%R %o %n %v' FreeBSD-src
FreeBSD-base base/FreeBSD-src FreeBSD-src 15.0.b1.20251016034928
[5-0] # pkg search -r FreeBSD-base FreeBSD-src
FreeBSD-src-15.0.b1.20251016034928 System userland source code
FreeBSD-src-sys-15.0.b1.20251015211959 System kernel source code
[6-0] # pkg version -r FreeBSD-base -n FreeBSD-src
Updating FreeBSD-base repository catalogue...
FreeBSD-base is up to date.
FreeBSD-src-15.0.b1.20251016034928 =
[7-0] #

----- Original Message -----
From: "Mark Millard" <marklmi@yahoo.com>
To: "Colin Percival" <cperciva@tarsnap.com>
Cc: "Patrick M. Hausen" <hausen@punkt.de>, "FreeBSD-STABLE Mailing
List" <freebsd-stable@freebsd.org>
Sent: Thursday, 16 October, 2025 23:16:53
Subject: 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 rCLenabledrCY status from repo.conf.
/usr/local/share/man/man8/pkg-search.8.gz: irrespective of the configured rCLenabledrCY 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.

Above is where I indicated that the context was
"not something that is (yet?) a pkgbase'd
[i]nstallation". (It is still not pkgbased.)

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 rCo 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 rCLenabledrCY 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
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2