Date: Fri, 08 Dec 2023 13:21:43 -0600 From: robert@rrbrussell.com To: freebsd-questions@freebsd.org Subject: Re: pkg killed on FreeBSD upgrade to 14 Message-ID: <a85d66a9-528a-4b90-ac4b-a204009da334@app.fastmail.com> In-Reply-To: <d990e8a3-e84f-4965-95bf-f3abf21ac96f@fjl.co.uk> References: <d990e8a3-e84f-4965-95bf-f3abf21ac96f@fjl.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
pkg-static bootstrap -f will force an upgrade of pkg from the package re= pository. After that several rounds of portmaster -af should find all th= e breakages. I have found poudri=C3=A8re to be more reliable at rebuilding everything= than portmaster. On Fri, Dec 8, 2023, at 12:43, Frank Leonhardt wrote: > I'm not sure whether this is a question or a warning. > > I upgraded my "latest" FreeBSD box to 14.0-RELEASE. It basically runs=20 > local DNS and a DHCP server so it's not a huge deal if it's trashed, a= nd=20 > is therefore the first to get upgraded. It was originally installed wi= th=20 > 12.0 and has been updated to everything in between. > > I got "bad vibes" going to from 13.2->14.0 - warnings that seemed=20 > reasonable about stuff missing from /src/ and suchlike that I didn't=20 > expect to see, but no actual errors as far as I could tell. > > On completion, however, pkg was no longer working - the following erro= r=20 > message: > > 'ld-elf.so.1: Shared object "libssl.so.111" not found, required by "pk= g"' > > My suspicion is that this was something to do with OpenSSL being updat= ed=20 > in 14.0 but I decided I'd had enough and did a (successful) rollback=20 > rather than trying to figure it out and relinking libraries. > > Has anyone else had the same problem, and what are the runes to avoid = it=20 > should I decide to have another go? > > Thanks, Frank.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a85d66a9-528a-4b90-ac4b-a204009da334>