FreeBSD 14.1

fernandel

fernandel

Hi!

I did upgrade 14.0-RELEASE to 14.1 on Lenovo laptop T495 with freebsd-update and everything was good. I am using packages (just few I buld from ports). I try to install
graphics/drm-61-kmod but pkg is not available and in ports is version for 14.1-STABLE. Looks like that is to early to update packages.
 
Someday we could get versioned packages... Until that day, the front page of FreeBSD could just say "current release": 14.0 and refer to the version that packages are built against.
 
fernandel said:
in ports is version for 14.1-STABLE
Click to expand...
Code: 
.if ${OPSYS} == FreeBSD && !( ${OSVERSION} >= 1500008 || ( ${OSVERSION} >= 1400508 && ${OSVERSION} < 1500000 ))
IGNORE=		not supported on older than 14-STABLE 1400508, no kernel support
.endif
Any version above 1400508 (and less than 1500000) will do. 14.1-RELEASE is 1401000, which is higher than 1400508. That means this port can be installed on 14.1-RELEASE.
 
fernandel said:
Hi!

I did upgrade 14.0-RELEASE to 14.1 on Lenovo laptop T495 with freebsd-update and everything was good. I am using packages (just few I buld from ports). I try to install
graphics/drm-61-kmod but pkg is not available and in ports is version for 14.1-STABLE. Looks like that is to early to update packages.
Click to expand...

The ports version automatically adapts so to speak. There is no 14.1-STABLE specific version in ports.

Just compile the port and you'll be fine.
 
Just my thought.
All -kmod pkgs should be stopped providing and force building locally from ports on freebsd-update and/or src upgrading to avoid mismatches.
This also means kernel sources and (at least minimal part to sanely build -kmod ports) ports tree should be forcibly included in base upgrade.

Without doing so, packages SHALL target the latest single updates, and previous .* release (this case, 14.0 for 14.1) / previous -p* update SHALL be obsoleted immediately after first -kmod pkgs are ready.

Why this kind of problems happen? Isn't API/KPI assured on stable and releng (release) branches? Yes. But ABI/KBI aren't, unfortunately and avoids -kmod ports to be loaded as incompatible. This is because I thing as above, unfortunately.
 
You must log in or register to reply here.
Back
Top