On Fri, 14 Nov 2025 23:19:37 +0100
Erichans <[email protected]> wrote:
> On 13/11/2025 08:31, Andriy Gapon wrote:
> > On 13/11/2025 01:17, Tomoaki AOKI wrote:
> > >> On Wed, Nov 12, 2025 at 03:28:28PM +0200, Andriy Gapon wrote:
> > >>> Main package repo-s and kmod repo-s are updated at independent cadences.
> > >>> Also, there can be build failures that can introduce further
> > >>> unpredictability into package update cycles.
> > >>> So, it can happen and has happened recently that nvidia packages got
> > >>> updated in one place but remained at an older version in the other.
> > >
> > > Hope this is an extraordinary situation in preparation of new
> > > *.0-Release. I'm not using official pkg repos, but IIRC, nvidia
> > > driver things on main repo are usually built quickly after commits.
> >
> > There is nothing extraordinary about this situation, it's a natural
> > consequence
> > of packages being in different repositories which are built independently.
> > It's bound to happen again.
> > So, it's better to prevent the desynchronization by means of pkg(8).
>
> When there are two supported minor releases of the same branch,
> you could find yourself in a no-man's-land scenario where
> *no workable set of packages* is available.
>
> For example, say that we are in the three-month overlap period of
> 14.3-RELEASE and 14.4-RELEASE and the Nvidia driver _packages_
> are in the process of transitioning from version:
>
> 580.95.05
> to
> 580.105.08
>
> On 14.3-RELEASE and 14.4-RELEASE respectively we have the following
> packages available.
> On 14.3-RELEASE:
>
> [0-0] # freebsd-version -r
> 14.3-RELEASE-p5
> [1-0] # pkg rquery -x '[%R] %o %n %v' '^drm-(61-)?kmod|(^nvidia-)' | \
> egrep -v 'nvidia-(driver|kmod|drm-515)-...|-devel|-settings|-xconfig|-tools'
> | \
> column -t
> [FreeBSD] graphics/drm-61-kmod drm-61-kmod
> 6.1.128.1403000_7
> [FreeBSD] graphics/drm-kmod drm-kmod 20250428
> [FreeBSD] x11/nvidia-driver nvidia-driver
> 580.95.05 <-- usable
> [FreeBSD] graphics/nvidia-drm-61-kmod nvidia-drm-61-kmod
> 580.95.05.1403000
> [FreeBSD] graphics/nvidia-drm-kmod nvidia-drm-kmod 580.95.05
> [FreeBSD] x11/nvidia-kmod nvidia-kmod
> 580.95.05.1403000 <-- usable
> [FreeBSD-kmods] graphics/drm-61-kmod drm-61-kmod
> 6.1.128.1403000_7
> [FreeBSD-kmods] x11/nvidia-kmod nvidia-kmod
> 580.105.08.1403000 <-- NOT usable
>
> On 14.4-RELEASE:
> [0-0] # freebsd-version -r
> 14.4-RELEASE
> [1-0] # pkg rquery -x '[%R] %o %n %v' '^drm-(61-)?kmod|(^nvidia-)' | \
> egrep -v 'nvidia-(driver|kmod|drm-515)-...|-devel|-settings|-xconfig|-tools'
> | \
> column -t
> [FreeBSD] graphics/drm-61-kmod drm-61-kmod
> 6.1.128.1403000_7
> [FreeBSD] graphics/drm-kmod drm-kmod 20250428
> [FreeBSD] x11/nvidia-driver nvidia-driver
> 580.95.05 <-- NOT usable
> [FreeBSD] graphics/nvidia-drm-61-kmod nvidia-drm-61-kmod
> 580.95.05.1403000
> [FreeBSD] graphics/nvidia-drm-kmod nvidia-drm-kmod 580.95.05
> [FreeBSD] x11/nvidia-kmod nvidia-kmod
> 580.95.05.1403000 <-- NOT usable
> [FreeBSD-kmods] graphics/drm-61-kmod drm-61-kmod
> 6.1.128.1404000_7
> [FreeBSD-kmods] x11/nvidia-kmod nvidia-kmod
> 580.105.08.1404000 <-- NOT usable
>
> "NOT usable" here means that the package cannot be used as a
> part of an aligned combination, given the available packages.
>
> For 14.4-RELEASE we should have —as a working set of packages—either:
> [FreeBSD] x11/nvidia-driver nvidia-driver 580.95.05
> [FreeBSD-kmods] x11/nvidia-kmod nvidia-kmod
> 580.95.05.1404000
>
> or
>
> [FreeBSD] x11/nvidia-driver nvidia-driver 580.105.08
> [FreeBSD-kmods] x11/nvidia-kmod nvidia-kmod
> 580.105.08.1404000
>
> Therefore, an aligned, working combination of nvidia-driver and
> nvidia-kmod cannot be installed from the remote repositories
> because neither combination is available. This will also affect
> pkg upgrade actions.
>
>
> Eric
As my usual email server (in shared hosting serivce) is blocked
by FreeBSD.org email server, temporarily subscribed with another one
on different service provider.
The best would be increasing resources for kmod builder to allow
previous style of x11/nvidia-driver* that contain both kmods and
remainders, but putting it aside.
It would be strongly adviced to perform dry-run before acutal
upgrading, and if whichever of x11/nvidia-kmod* or x11/nvidia-driver*
is / are upgraded but not yet for another, wait until both matches
or lock already upgraded one and unlock when confirmed the counterpart
is upgraded on dry-run.
--
Tomoaki AOKI
<[email protected]>
<[email protected]>
