Date: Thu, 21 May 2026 18:58:06 -0700 From: "Dan Mahoney (Ports)" <freebsd@gushi.org> To: Mike <the.lists@mgm51.com> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@FreeBSD.org> Subject: Re: Update for 14.3 when it is out of date - not pretty Message-ID: <48327133-A375-468B-B1FB-B87F847C9C51@gushi.org> In-Reply-To: <a3eea774-bf58-4f09-9a35-c64f9c50185e@mgm51.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] 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 It shouldn't say "rebuild". It's a bug, and I'd complain, if freebsd-update's days weren't Very Numbered. 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, -Dan > On May 21, 2026, at 6:32 PM, Mike <the.lists@mgm51.com> wrote: > > /usr/sbin/freebsd-update [-- Attachment #2 --] <html aria-label="message body"><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">You mean this warning?<div><br></div><div>```</div><div><div>Completing this upgrade requires removing old shared object files.</div><div>Please rebuild all installed 3rd party software (e.g., programs</div><div>installed from the ports tree) and then run</div><div>'`basename $0` [options] install' again to finish installing updates.</div><div>```</div><div><br></div><div>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:</div><div><br></div><div>pkg upgrade</div><div><br></div><div>It shouldn't say "rebuild". It's a bug, and I'd complain, if freebsd-update's days weren't Very Numbered.</div><div><br></div><div>What's going on:</div><div><br></div><div>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.</div><div><br></div><div>Hope this helps,</div><div><br></div><div>-Dan</div><div><br></div><div><br><blockquote type="cite"><div>On May 21, 2026, at 6:32 PM, Mike <the.lists@mgm51.com> wrote:</div><br class="Apple-interchange-newline"><div><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">/usr/sbin/freebsd-update</span></div></blockquote></div><br></div></body></html>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48327133-A375-468B-B1FB-B87F847C9C51>