Call for testing: pkgbase support in 15.0

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.
Click to expand...
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 ~]$
 
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 said:
FWIW, BETA1 is out but a simple pkg upgrade does not show anything available at the moment.
Click to expand...
fmc000 said:
View attachment 23853
Click to expand...
It is unclear to me where you are or where you want to be.
  1. Version string 1500066 belongs to stable/15, as OSVERSION = "1500066" in your screenshot shows.
  2. 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"
Click to expand...
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:
  1. FreeBSD 15.0-BETA1 Now Available - detailed description.
  2. 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
 
fmc000 said:
See my post #103.
Click to expand...
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 said:
Those other repositories weren't changed. Also, the warning provides you with the suggestion on how to fix it.
Click to expand...
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. 😅
 
Erichans said:
It is unclear to me where you are or where you want to be.
  1. Version string 1500066 belongs to stable/15, as OSVERSION = "1500066" in your screenshot shows.
  2. 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:
  1. FreeBSD 15.0-BETA1 Now Available - detailed description.
  2. 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
Click to expand...
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).
 
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 😁
 
You must log in or register to reply here.
Back
Top