Re: Update for 14.3 when it is out of date - not pretty

On 5/21/2026 9:58 PM, Dan Mahoney (Ports) wrote:
> You mean this warning?
> 
> ```
> Completing this upgrade requires removing old shared object files.
> Please rebuild all installed 3rd party software (e.g., programs
> installed from the ports tree) and then run
> '`basename $0` [options] install' again to finish installing updates.
> ```
> 
> This is sort of a bad warning because most people aren't using ports 
> these days, and what it really wants you to do is:
> 
> pkg upgrade

Yeah, I agree.

I'd nominate it for one of the worst warning messages thrown at a user 
during an OS upgrade.  But that is just me.

> 
> It shouldn't say "rebuild".  It's a bug, and I'd complain, if freebsd- 
> update's days weren't Very Numbered.

While I tried not to complain, I did want to note the issue.

> 
> What's going on:
> 
> Most often, binary upgrades are still compatible with the old releases, 
> so (for example) sshd will start in a space where you have a 14.4 kernel 
> and a 14.3 userland, but at some point, programs in /usr/local/bin that 
> were built and compiled for things in /lib and /usr/lib (etc) have old 
> version numbers, so on the next reboot, those things won't work.  The 
> update process leaves the "vestigial" shared libraries in place so 
> things don't crash, until the third "freebsd-update install" at which 
> point it rm's everything that would have been i n $oldversion but not 
> $currentversion.
> 
> Hope this helps,

It did help.

Many thanks.

And, fwiw, I am [slowly] moving my FreeBSD servers over to use the new 
package update facility.

I do have to mention that major issues. such as this update that caused 
me to re-install my server. give me a concern about a leap into a 
pkg-based system update.

But that is the future.


Thanks again for your reply.