Re: pkg killed on FreeBSD upgrade to 14

On 12/8/23 2:25 PM, Frank Leonhardt wrote:
> On 08/12/2023 19:21, robert@rrbrussell.com wrote:
>> On Fri, Dec 8, 2023, at 12:43, Frank Leonhardt wrote:
>>> <snip>
>>> I got "bad vibes" going to from 13.2->14.0 - warnings that seemed
>>> reasonable about stuff missing from /src/ and suchlike that I didn't
>>> expect to see, but no actual errors as far as I could tell.
>>>
>>> On completion, however, pkg was no longer working - the following error
>>> message:
>>>
>>> 'ld-elf.so.1: Shared object "libssl.so.111" not found, required by "pkg"'
>>> <snip>
>>>
>>> Has anyone else had the same problem, and what are the runes to avoid it
>>> should I decide to have another go?
>>> <snip>
>> pkg-static bootstrap -f will force an upgrade of pkg from the package repository. After that several rounds of portmaster -af should find all the breakages.
>>
>> I have found poudrière to be more reliable at rebuilding everything than portmaster.
>>
> Thanks - I could could find an install the relevant library manually, 
> but I want to know *why* a standard upgrade on a vanilla installation 
> broke. Are there any undocumented pre-upgrade steps. Good idea to use 
> pkg-static to recover pkg, but I took this as a bad sign and did a 
> rollback. I suspect there was more than just this wonky about it.The 
> certificate login was also broken, and I'm sure csh being swapped out 
> would cause trouble too :-(
> 


It's standard practice to upgrade pkg itself before updating any other 
packages when doing any major updates to a freebsd release.

The docs may need to be clarified around this, but the standard 
operating procedure IMHO is after you've updated your kernel and 
userland with a new major version the first step is to "pkg-static 
upgrade" which should make sure all of the correct libraries for pkg are 
in place.


-pete


-- 
Pete Wright
pete@nomadlogic.org