Solved Question about a pkg's FreeBSD_version after upgrading with pkgbase

Hi,

I followed the upgrading instructions for pkgbase and everything went fine.
Now I look at none-base pkgs and notice:
Code:
pkg info btop   
btop-1.4.6
Name           : btop
Version        : 1.4.6
Installed on   : Mon Apr  6 15:59:14 2026 CEST
Origin         : sysutils/btop
Architecture   : FreeBSD:15:amd64
Prefix         : /usr/local
Categories     : sysutils
Licenses       : APACHE20
Maintainer     : pkubaj@FreeBSD.org
WWW            : https://github.com/aristocratos/btop
Comment        : Monitor of resources
Shared Libs required:
    libc++.so.1
    libc.so.7
    libcxxrt.so.1
    libdevstat.so.7
    libgcc_s.so.1
    libkvm.so.7
    libm.so.5
    libthr.so.3
Annotations    :
    FreeBSD_version: 1500068

FreeBSD_version for that pkg is 1500068. Other pkg's which got upgraded from pkgbase have the new version:

Code:
pkg info FreeBSD-zfs     
FreeBSD-zfs-15.1
Name           : FreeBSD-zfs
Version        : 15.1
Installed on   : Sat Jun 20 17:11:53 2026 CEST
Origin         : base/FreeBSD-zfs
Architecture   : FreeBSD:15:amd64
Prefix         : /
Categories     : base
Licenses       : CDDL-1.0
Maintainer     : re@FreeBSD.org
WWW            : https://www.FreeBSD.org
Comment        : ZFS filesystem support
Shared Libs required:
    libavl.so.2
    libbe.so.1
    libbsdxml.so.4
    libc++.so.1
    libc.so.7
    libcrypto.so.35
    libcxxrt.so.1
    libgcc_s.so.1
    libgeom.so.5
    libicp.so.3
    libjail.so.1
    libm.so.5
    libnvpair.so.2
    libpam.so.6
    libprivatedevdctl.so.0
    libsbuf.so.6
    libspl.so.2
    libthr.so.3
    libtpool.so.2
    libumem.so.2
    libutil.so.10
    libuutil.so.2
    libzdb.so.2
    libzfs.so.4
    libzfs_core.so.2
    libzfsbootenv.so.1
    libzpool.so.2
    libzutil.so.2
Annotations    :
    FreeBSD_version: 1501000
FreeBSD_version is 1501000 here.

The upgrade instructions for Distribution Sets contain a sentence: "freebsd-update(8) may prompt to rebuild or reinstall all third-party software due to changes in system libraries."
This seems not to be the case while upgrading with pkgbase.

Code:
doas pkg update     
Updating FreeBSD-ports repository catalogue...
FreeBSD-ports repository is up to date.
Updating FreeBSD-ports-kmods repository catalogue...
FreeBSD-ports-kmods repository is up to date.
Updating FreeBSD-base repository catalogue...
FreeBSD-base repository is up to date.
All repositories are up to date.

doas pkg upgrade
Updating FreeBSD-ports repository catalogue...
FreeBSD-ports repository is up to date.
Updating FreeBSD-ports-kmods repository catalogue...
FreeBSD-ports-kmods repository is up to date.
Updating FreeBSD-base repository catalogue...
FreeBSD-base repository is up to date.
All repositories are up to date.
Checking for upgrades (0 candidates): 100%
Processing candidates (0 candidates): 100%
Checking integrity... done (0 conflicting)
Your packages are up to date.

Code:
freebsd-version -kru
15.1-RELEASE
15.1-RELEASE
15.1-RELEASE

Do I get this right: FreeBSD_version shows on which FreeBSD version the pkg got installed (15.0 in this case). If I would want to show it FreeBSD_version = 1501000 (15.1-RELEASE) I would need to force re-install the pkg?
Is that even necessary? Does it matter?
Will it show the new version after an update of the pkg?

Thanks!
 
FreeBSD_version for that pkg is 1500068.
This is fine. For userland applications the ABI stays stable within the same major version. So applications built on/for 15.0 will work on 15.1 without issues.

Will it show the new version after an update of the pkg?
For the next three months the FreeBSD packages will be built for 15.0, because that's the lowest supported version. After this three month 'grace' period 15.0 will be EoL and the FreeBSD package repositories will start building packages with 15.1.
 
Back
Top