Call for testing: pkgbase support in 15.0

rbranco · 2025-10-12T17:53:06+0100

Habemvs BETA1 packages:

Re: FreeBSD 15.0-BETA1 Now Available [ use url: "pkg+https://pkg.FreeBSD.org/${ABI}/base_release_0", ]

I'll stay on 15-STABLE. See ya.

Useradd · 2025-10-12T19:24:40+0100

rbranco said:
Habemvs BETA1 packages:
Re: FreeBSD 15.0-BETA1 Now Available [ use url: "pkg+https://pkg.FreeBSD.org/${ABI}/base_release_0", ]

I tried that and the freebsd-* packages were downgraded to 15.snap20251011015136. uname -r now shows 15.0-STABLE. Apart from that, everything seems to be working still but I'm not sure I know what I'm doing so I'll take a break and think about it for a while.

fmc000 · 2025-10-12T19:30:40+0100

Useradd said:
I tried that and the freebsd-* packages were downgraded to 15.snap20251011015136. uname -r now shows 15.0-STABLE. Apart from that, everything seems to be working still but I'm not sure I know what I'm doing so I'll take a break and think about it for a while.

Pretty strange because I did exactly what was suggested by Colin and now all my packages are like FreeBSD-kernel-generic-15.0.b1.20251012072228 and

Code:

[20:28][fmc000@tu45b-freebsd ~]$ uname -r       
15.0-BETA1
[20:29][fmc000@tu45b-freebsd ~]$

I suspect you're doing something wrong.

Code:

[20:29][fmc000@tu45b-freebsd ~]$ cat /usr/local/etc/pkg/repos/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
}
[20:30][fmc000@tu45b-freebsd ~]$

T-Aoki · 2025-10-13T00:05:38+0100

fmc000 said:
Pretty strange because I did exactly what was suggested by Colin

This post in freebsd-stable ML?

scottro · 2025-10-13T00:26:26+0100

Like one of the posters on that list, I did pkg upgrade on an ALPHA and didn't get BETA. But unlike them, I just got lazy, wiped it and installed BETA. At present, I'm more concerned about will my usual programs (do the young folk call 'em apps these days?) run. And for actual upgrades, I'm more concerned about updating 14.x to 15. Which, to be honest, I guess is me trying to excuse being lazy.

Oh, and 15.0 was fine, my window manager worked, alcritty works. That's all I tried. I didn't test video and sound yet, but as they've worked on the 15-ALPHA's I'd be surprised if I have an issue. (Hope I didn't just jinx myself).

fmc000 · 2025-10-13T00:48:55+0100

T-Aoki said:
This post in freebsd-stable ML?

Changing the URL to: url: "pkg+https://pkg.FreeBSD.org/${ABI}/base_release_0",

Erichans · 2025-10-13T02:04:25+0100

fmc000 said:
FWIW, BETA1 is out but a simple pkg upgrade does not show anything available at the moment.

fmc000 said:
View attachment 23853

It is unclear to me where you are or where you want to be.

Version string 1500066 belongs to stable/15, as OSVERSION = "1500066" in your screenshot shows.
If you are on BETA1, you should have version string 1500067; that belongs to releng/15

Also, using:

fmc000 said:
Changing the URL to: url: "pkg+https://pkg.FreeBSD.org/${ABI}/base_release_0"

indicates you "want to be"/are on BETA1. If you've stayed on stable/15 and upgraded that branch successfully, your version string should now be 150050.

Being on stable/15 versus releng/15 requires different package repository settings. If you've successfully upgraded/installed BETA1, for the repositories FreeBSD-ports and FreeBSD-ports-kmods the relevant .conf settings for quarterly (as per default defined in FreeBSD.conf.quarterly-release) are:

Rich (BB code):

FreeBSD-ports: {
    url: pkg+https://pkg.freebsd.org/${ABI}/quarterly,
   [...]
}
FreeBSD-ports-kmods: {
    url: pkg+https://pkg.freebsd.org/${ABI}/kmods_quarterly_${VERSION_MINOR},
   [...]
}

The relevant .conf settings for latest are:

Rich (BB code):

FreeBSD-ports: {
    url: pkg+https://pkg.freebsd.org/${ABI}/latest,
   [...]
}
FreeBSD-ports-kmods: {
    url: pkg+https://pkg.freebsd.org/${ABI}/kmods_latest_${VERSION_MINOR},
   [...]
}

Please note:

FreeBSD 15.0-BETA1 Now Available - detailed description.
manual action required updating from 15.0-ALPHA to 15-STABLE with pkgbase - freebsd-pkgbase ML message.

Furthermore, it seems that at the moment no FreeBSD-ports-kmods repository is set up for releng/15, https://pkg.freebsd.org/FreeBSD:15:amd64/:

Code:

Index of /FreeBSD:15:amd64/
File Name  ↓ 	    File Size  ↓   Date  ↓ 
Parent directory/	-              -
base_latest/	    -              2025-Oct-12 12:05
base_release_0/	    -              2025-Oct-12 12:05
base_weekly/	    -              2025-Oct-12 12:05
kmods_latest/	    -              2025-Oct-13 00:00
kmods_quarterly/	-              2025-Oct-13 00:00
latest/	            -              2025-Oct-09 16:15
quarterly/	        -              2025-Oct-09 12:52

No kmods_quarterly_0 and kmods_latest_0 present.

Compare that for example with https://pkg.freebsd.org/FreeBSD:14:amd64/, for 14.3-RELEASE:

Code:

Index of /FreeBSD:14:amd64/
File Name  ↓ 	    File Size  ↓   Date  ↓ 
Parent directory/	-              -
   [...]
kmods_latest_3/	    -              2025-Oct-12 12:05
   [...]
kmods_quarterly_3/	-              2025-Oct-12 12:05

T-Aoki · 2025-10-13T02:24:15+0100

Erichans said:
It is unclear to me where you are or where you want to be.

My understanding is that fmc000 wants to upgrade to 15.0-BETA1 via pkgbase, thus, I had no doubts with the __FreeBSD_version.

fmc000 · 2025-10-13T02:32:46+0100

I _have_ upgraded to 15.0-BETA1 on two of my systems. Both work perfectly fine.See my post #103.

Useradd · 2025-10-13T08:07:53+0100

fmc000 said:
See my post #103.

Yes, I did that, but what about the other two repositories: FreeBSD-ports and FreeBSD-ports-kmods? Don't I have to change something there?

I have just done a fresh install from the iso image, but if I want to install an application such as nano, I still get the warning about package 1500500 while running userland 1500067.

The first time I run pkg upgrade pkg-2.3.1 is installed automatically.

fmc000 · 2025-10-13T08:16:25+0100

Those other repositories weren't changed. Also, the warning provides you with the suggestion on how to fix it.

Useradd · 2025-10-13T08:36:59+0100

fmc000 said:
Those other repositories weren't changed. Also, the warning provides you with the suggestion on how to fix it.

The warning suggests how to ignore the error, but I would just like to be sure about this so I don't mess up the installation and have to start all over again.

fmc000 · 2025-10-13T08:40:56+0100

Useradd said:
The warning suggests how to ignore the error, but I would just like to be sure about this so I don't mess up the installation and have to start all over again.

You just answer "Y" and proceed. You won't be forced to install anything.

Useradd · 2025-10-13T08:44:06+0100

fmc000 said:
You just answer "Y" and proceed. You won't be forced to install anything.

Yes, it worked! Thank you for your help (and your patience).

fmc000 · 2025-10-13T08:48:57+0100

Erichans said:
It is unclear to me where you are or where you want to be.

Version string 1500066 belongs to stable/15, as OSVERSION = "1500066" in your screenshot shows.

If you are on BETA1, you should have version string 1500067; that belongs to releng/15

Also, using:

indicates you "want to be"/are on BETA1. If you've stayed on stable/15 and upgraded that branch successfully, your version string should now be 150050.

Being on stable/15 versus releng/15 requires different package repository settings. If you've successfully upgraded/installed BETA1, for the repositories FreeBSD-ports and FreeBSD-ports-kmods the relevant .conf settings for quarterly (as per default defined in FreeBSD.conf.quarterly-release) are:

Rich (BB code):

FreeBSD-ports: { url: pkg+https://pkg.freebsd.org/${ABI}/quarterly, [...] } FreeBSD-ports-kmods: { url: pkg+https://pkg.freebsd.org/${ABI}/kmods_quarterly_${VERSION_MINOR}, [...] }

The relevant .conf settings for latest are:

Rich (BB code):

FreeBSD-ports: { url: pkg+https://pkg.freebsd.org/${ABI}/latest, [...] } FreeBSD-ports-kmods: { url: pkg+https://pkg.freebsd.org/${ABI}/kmods_latest_${VERSION_MINOR}, [...] }

Please note:

FreeBSD 15.0-BETA1 Now Available - detailed description.

manual action required updating from 15.0-ALPHA to 15-STABLE with pkgbase - freebsd-pkgbase ML message.

Furthermore, it seems that at the moment no FreeBSD-ports-kmods repository is set up for releng/15, https://pkg.freebsd.org/FreeBSD:15:amd64/:

Code:

Index of /FreeBSD:15:amd64/ File Name ↓ File Size ↓ Date ↓ Parent directory/ - - base_latest/ - 2025-Oct-12 12:05 base_release_0/ - 2025-Oct-12 12:05 base_weekly/ - 2025-Oct-12 12:05 kmods_latest/ - 2025-Oct-13 00:00 kmods_quarterly/ - 2025-Oct-13 00:00 latest/ - 2025-Oct-09 16:15 quarterly/ - 2025-Oct-09 12:52

No kmods_quarterly_0 and kmods_latest_0 present.

Compare that for example with https://pkg.freebsd.org/FreeBSD:14:amd64/, for 14.3-RELEASE:

Code:

Index of /FreeBSD:14:amd64/ File Name ↓ File Size ↓ Date ↓ Parent directory/ - - [...] kmods_latest_3/ - 2025-Oct-12 12:05 [...] kmods_quarterly_3/ - 2025-Oct-12 12:05

This just means that no kmods packages were created for BETA-1 so far and thus ALPHA-5 packages will be used instead. I don't see the problem actually.

Code:

[9:41][fmc000@tu45b-freebsd ~]$ uname -a
FreeBSD tu45b-freebsd 15.0-BETA1 FreeBSD 15.0-BETA1 releng/15.0-n280655-36a923a476dc GENERIC amd64
[9:47][fmc000@tu45b-freebsd ~]$ uname -KrU
15.0-BETA1 1500067 1500067
[9:47][fmc000@tu45b-freebsd ~]$ li kmod
drm-latest-kmod-6.9.1500066    DRM drivers modules
gpu-firmware-intel-kmod-tigerlake-20230625.1500066 Firmware modules for tigerlake Intel GPUs
virtualbox-ose-kmod-72-7.2.2.1500066 VirtualBox kernel module for FreeBSD
wifi-firmware-iwlwifi-kmod-ax210-20241017.1500066_2 Firmware modules for the iwlwifi (ax210) WiFi NIC driver
[9:48][fmc000@tu45b-freebsd ~]$

( li is just an alias for installed packages).

vmisev · 2025-10-13T09:12:16+0100

So, I tried 15.0-BETA1. I failed miserably at first, but as kids nowadays say:
!!!!! IT WAS ENTIRELY MY FAULT !!!!!

I tried it in VBox VM (my main desktop is still booted in Alt, still busy compiling 6.16.7 for aarch64 Gentoo in QEMU – don't ask!), but I started with ridiculously low space for a such action, just over 4G free on .vdi

I tried with deleting some stuff that I don't need there, made some more space, but pkg was failing with "cannot start a transaction within a transaction".

Okay then, time to call for aerial and artillery support – shut VM down, increase size, detach .vdi, shut VBox down, convert .vdi to --fixed, rename it back to original name, reattach, boot single user, gpart -i , zpool -e , and there is a space to maneuver.

This time I started with edited /etc/pkg/FreeBSD.conf with three separate repos for base, ports and kmods, but I went with freebsd-update upgrade -r 15*, and after second freebsd-update install I did pkg bootstrap -f, pkg update -r FreeBSD-ports and sqllite3 \ .recover on local.sqlite.

!!!! pkg upg -r FreeBSD-ports -f !!!! did its job without a hitch (with /$(ABI)/latest)

Only problem I had was with FreeBSD-ports-kmods refusing to update, but after some debugging, and after removing _${VERSION_MINOR} in .../$(ABI)/kmods_latest line, pkg upg -r FreeBSD-ports-kmods succeeded!

All in all, looks like that all in 15.0-BETA1 works perfectly (including X/Plasma6 and other stuff) and that pkgbase is not such a boogeyman after all

doddi · 2025-10-13T09:43:25+0100

victort said:
Wait, does it not use the host configuration repos? Or does it use whatever is inside the $rootdir?

It uses the host configuration repos but looks for keys inside $rootdir, which we think is a bug.

T-Aoki · 2025-10-13T11:37:00+0100

Someone would be interested in this post to freebsd-stable ML by Lexi Winter.

Useradd · 2025-10-13T18:14:36+0100

I did a clean install of 15.0-ALPHA5 (Packages option) and it gave me 15.0-STABLE (which is good), but when I installed xorg and nvidia-driver in the usual way I get this after reboot:

Code:

NVRM: API mismatch: the client 'Xorg' (pid 8105)
NVRM: has the version 580.82.07, but this kernel module has
NVRM: the version 580.95.05. Please make sure that this
NVRM: kernel module and all NVIDIA driver components
NVRM: have the same version.

T-Aoki · 2025-10-13T18:22:05+0100

Useradd said:
I did a clean install of 15.0-ALPHA5 (Packages option) and it gave me 15.0-STABLE (which is good), but when I installed xorg and nvidia-driver in the usual way I get this after reboot:

Code:

NVRM: API mismatch: the client 'Xorg' (pid 8105) NVRM: has the version 580.82.07, but this kernel module has NVRM: the version 580.95.05. Please make sure that this NVRM: kernel module and all NVIDIA driver components NVRM: have the same version.

This would be because FreeBSD-ports-kmod repo has updated x11/nvidia-kmod alone

Code:

# pkg search -r FreeBSD-ports-kmods nvidia
nvidia-kmod-580.95.05.1500500  kmod part of NVidia graphics card binary drivers for hardware OpenGL rendering
#

While FreeBSD-ports repo doesn't yet have 580.95.05.

Code:

# pkg search -r FreeBSD-ports nvidia
libva-nvidia-driver-0.0.14_2   NVDEC-based backend for VAAPI
linux-nvidia-libs-580.82.07    NVidia graphics libraries and programs (Linux version)
linux-nvidia-libs-304-304.137  NVidia graphics libraries and programs (Linux version)
linux-nvidia-libs-340-340.108  NVidia graphics libraries and programs (Linux version)
linux-nvidia-libs-390-390.157  NVidia graphics libraries and programs (Linux version)
linux-nvidia-libs-470-470.256.02 NVidia graphics libraries and programs (Linux version)
linux-nvidia-libs-devel-580.82.07 NVidia graphics libraries and programs (Linux version)
nvidia-driver-580.82.07_1      NVidia graphics card binary drivers for hardware OpenGL rendering
nvidia-driver-304-304.137_11   NVidia graphics card binary drivers for hardware OpenGL rendering
nvidia-driver-340-340.108_5    NVidia graphics card binary drivers for hardware OpenGL rendering
nvidia-driver-390-390.157_1    NVidia graphics card binary drivers for hardware OpenGL rendering
nvidia-driver-470-470.256.02_2 NVidia graphics card binary drivers for hardware OpenGL rendering
nvidia-driver-devel-580.82.07_1 NVidia graphics card binary drivers for hardware OpenGL rendering
nvidia-drm-61-kmod-580.82.07.1500066_5 NVIDIA DRM Kernel Module
nvidia-drm-61-kmod-devel-580.82.07.1500066_5 NVIDIA DRM Kernel Module
nvidia-drm-66-kmod-580.82.07.1500066_5 NVIDIA DRM Kernel Module
nvidia-drm-66-kmod-devel-580.82.07.1500066_5 NVIDIA DRM Kernel Module
nvidia-drm-kmod-580.82.07_1    NVIDIA DRM Kernel Module
nvidia-drm-kmod-devel-580.82.07_1 NVIDIA DRM Kernel Module
nvidia-kmod-580.82.07.1500066  kmod part of NVidia graphics card binary drivers for hardware OpenGL rendering
nvidia-kmod-304-304.137.1500066 kmod part of NVidia graphics card binary drivers for hardware OpenGL rendering
nvidia-kmod-340-340.108.1500066 kmod part of NVidia graphics card binary drivers for hardware OpenGL rendering
nvidia-kmod-390-390.157.1500066 kmod part of NVidia graphics card binary drivers for hardware OpenGL rendering
nvidia-kmod-470-470.256.02.1500066 kmod part of NVidia graphics card binary drivers for hardware OpenGL rendering
nvidia-kmod-devel-580.82.07.1500066 kmod part of NVidia graphics card binary drivers for hardware OpenGL rendering
nvidia-settings-580.82.07      Display Control Panel for X NVidia driver
nvidia-texture-tools-2.1.2     Texture Tools with support for DirectX 10 texture formats
nvidia-xconfig-580.82.07       Tool to manipulate X configuration files for the NVidia driver
nvidia_gpu_prometheus_exporter-g20181028_31 NVIDIA GPU Prometheus exporter
#

Note that these are run on stable/15.

Deinstalling nvidia-kmod and update again with
pkg upgrade -r FreeBSD-ports
would help.

Useradd · 2025-10-13T18:46:09+0100

T-Aoki said:
Deinstalling nvidia-kmod and update again with
pkg upgrade -r FreeBSD-ports
would help.

I tried that but it didn't change anything. It says all the repository catalogues are up to date.
Their URLs are all configured to their respective "_latest" versions. Should I change the FreeBSD-base URL to "base_release_0" maybe?

I'm cautious about this after wrecking my previous fully configured 15.0-ALPHA5 and 15.0-BETA1 installations by running pkg upgrade on them later. (This is why I am installing 15.0-ALPHA5 now.)

T-Aoki · 2025-10-13T18:54:08+0100

Useradd said:
I tried that but it didn't change anything. It says all the repository catalogues are up to date.
Their URLs are all configured to their respective "_latest" versions. Should I change the FreeBSD-base URL to "base_release_0" maybe?

I'm cautious about this after wrecking my previous fully configured 15.0-ALPHA5 and 15.0-BETA1 installations by running pkg upgrade on them later. (This is why I am installing 15.0-ALPHA5 now.)

Now is the "confusing" timing.
stabe/15 which ALPHA* tracked defaults to latest ports, while releng/15.0 which BETA* and upcoming RC*, 15.0-Release are built from defaults to quarterly (now 2025Q5) ports.
Both branch of ports already have 580.95.05 (with possible security reason, unlike normally, it was merged into 2025Q4), but builds would be still ongoing on both.

And more, "base_release_0" is for pkgbase, not for ports.

Useradd · 2025-10-13T19:15:31+0100

TL;DR It isn't urgent, but if problems occur with both amdgpu and nvidia-kmod at the same time, then it's a real problem.

T-Aoki said:
And more, "base_release_0" is for pkgbase, not for ports.

I thought so.

T-Aoki said:
Now is the "confusing" timing.

I can wait a bit. I'm doing this on my test machine which I use to test upgrades which might impact my main PC, which would be a disaster. I have even tried reinstalling 14.3-RELEASE on my test machine but that fails too now because of the Nvidia driver change.

My main PC (with the AMD GPU) has both 15.0-STABLE and 14.3-RELEASE installed and they are still working fine. In the past I had problems there when upgrading 14.1-RELEASE to 14.2-RELEASE, but my test machine with its Nvidia card was unaffected.

T-Aoki · 2025-10-13T19:25:10+0100

Useradd said:
I'm doing this on my test machine which I use to test upgrades which might impact my main PC, which would be a disaster.

It's wise thing and should be done whenever possible.
But ZFS allows us to easily rolling back (from installation media or another installation on the same computer, at worst) if necessary snapshots are created before upgrading.

Useradd said:
I have even tried reinstalling 14.3-RELEASE on my test machine but that fails too now because of the Nvidia driver change.

It wouldn't be the change itself, just still builds are not yet finished with some reason.

Useradd said:
In the past I had problems there when upgrading 14.1-RELEASE to 14.2-RELEASE, but my test machine with its Nvidia card was unaffected.

If you don't use graphics/nvidia-drm-*-kmod, x11/nvidia-kmod (formerly a part of x11/nvidia-driver) is relatively robust on minor version upgrades of base, unlike anything depending upon LinuxKPI. So it could help you.

But the cases "now" includes switches of quarterly branch from 2025Q3 to 2025Q4, so many things are actually upgraded and take a fair amount of days to finish builds for all supported versions and archs concurrently.

fmc000 · 2025-10-13T19:36:41+0100

In short, if you want to track 15.0-STABLE right now there are a few modules that are not ready yet (i.e. virtualbox-ose-kmod-72-7.2.2 and possibly others). If you want to track releng/15.0 you have to disable the FreeBSD-ports-kmods repository because it still doesn't exist. However, the FreeBSD-ports repository has all the previous ALPHA kmods and they work just fine with BETA1, or at least on my installation I have:

Code:

drm-66-kmod-6.6.25.1500066_5   Direct Rendering Manager GPU drivers
gpu-firmware-intel-kmod-tigerlake-20230625.1500066 Firmware modules for tigerlake Intel GPUs
virtualbox-ose-kmod-72-7.2.2.1500066 VirtualBox kernel module for FreeBSD
wifi-firmware-iwlwifi-kmod-ax210-20241017.1500066_2 Firmware modules for the iwlwifi (ax210) WiFi NIC driver

and all of them work. I tried to track 15.0-STABLE but I went back to releng/15.0 when I noticed that I couldn't use my VMs (and, BTW, the situation is actually worse as even when I compiled the kmod from the ports it wouldn't load despite being at the correct OSVERSION).