Date: Wed, 20 Sep 2023 09:55:07 -0400 From: Garrett Wollman <wollman@bimajority.org> To: Pete French <pete@twisted.org.uk> Cc: stable@freebsd.org Subject: Re: Build of 14 on 13 creates a file which needs libdialog.so.9 Message-ID: <25866.63931.709389.553955@hergotha.csail.mit.edu> In-Reply-To: <E1qiw0t-00048P-9E@toybox.twisted.org.uk> References: <8474d23f-8551-474d-94d0-3fb04183b01b@aetern.org> <E1qiw0t-00048P-9E@toybox.twisted.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Wed, 20 Sep 2023 12:09:03 +0000, Pete French <pete@twisted.org.uk> said: > Possibly what I am doing is not supported, but I am a bit surprised as my > usual upgrade procedure is to build on one machine and then either NSF mount, > or rsync, the files to the boxes on which I wish to install them. This absolutely works, but only so long as all of the clients are running the same release as your build machine _was_ running during the most recent buildworld. I ran into this recently during our upgrade from 12.4 to 13.2, which saw a security update released while we were in the middle of rollout: I had to roll back /usr/src and /usr/obj to the 13.2-p1 state, roll out all the clients, and then I could (re)compile 13.2-p2 and deploy that -- by which point 13.2-p3 had come out, but by then we were over the hump. I think it's a bug in installworld that it depends on binaries from the build environment rather than the execution environment. -GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?25866.63931.709389.553955>