From nobody Fri Dec 08 22:25:21 2023
X-Original-To: questions@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Sn5LK1xbVz53WY0
	for <questions@mlmmj.nyi.freebsd.org>; Fri,  8 Dec 2023 22:25:13 +0000 (UTC)
	(envelope-from freebsd-doc@fjl.co.uk)
Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196])
	by mx1.freebsd.org (Postfix) with ESMTP id 4Sn5LJ3h0Cz4Yy6
	for <questions@freebsd.org>; Fri,  8 Dec 2023 22:25:12 +0000 (UTC)
	(envelope-from freebsd-doc@fjl.co.uk)
Authentication-Results: mx1.freebsd.org;
	dkim=none;
	spf=pass (mx1.freebsd.org: domain of freebsd-doc@fjl.co.uk designates 84.45.41.196 as permitted sender) smtp.mailfrom=freebsd-doc@fjl.co.uk;
	dmarc=none
Received: from [192.168.1.178] (host81-132-21-238.range81-132.btcentralplus.com [81.132.21.238])
	(authenticated bits=0)
	by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id 3B8MPBYm043649
	for <questions@freebsd.org>; Fri, 8 Dec 2023 22:25:11 GMT
	(envelope-from freebsd-doc@fjl.co.uk)
Content-Type: multipart/alternative;
 boundary="------------bIp731yCGNeEXNbHAbVNoBvm"
Message-ID: <1ba6fb31-9a43-47fa-aa0e-721e179c7317@fjl.co.uk>
Date: Fri, 8 Dec 2023 22:25:21 +0000
List-Id: User questions <freebsd-questions.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-questions
List-Help: <mailto:questions+help@freebsd.org>
List-Post: <mailto:questions@freebsd.org>
List-Subscribe: <mailto:questions+subscribe@freebsd.org>
List-Unsubscribe: <mailto:questions+unsubscribe@freebsd.org>
Sender: owner-freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
From: Frank Leonhardt <freebsd-doc@fjl.co.uk>
Subject: Re: pkg killed on FreeBSD upgrade to 14
To: questions@freebsd.org
References: <d990e8a3-e84f-4965-95bf-f3abf21ac96f@fjl.co.uk>
 <a85d66a9-528a-4b90-ac4b-a204009da334@app.fastmail.com>
Content-Language: en-GB
In-Reply-To: <a85d66a9-528a-4b90-ac4b-a204009da334@app.fastmail.com>
X-Spamd-Result: default: False [1.81 / 15.00];
	NEURAL_SPAM_LONG(1.00)[1.000];
	NEURAL_SPAM_MEDIUM(0.94)[0.943];
	R_SPF_ALLOW(-0.20)[+ip4:84.45.41.196:c];
	MIME_GOOD(-0.10)[multipart/alternative,text/plain];
	RCVD_NO_TLS_LAST(0.10)[];
	ONCE_RECEIVED(0.10)[];
	NEURAL_HAM_SHORT(-0.04)[-0.040];
	XM_UA_NO_VERSION(0.01)[];
	RCVD_COUNT_ONE(0.00)[1];
	R_DKIM_NA(0.00)[];
	MIME_TRACE(0.00)[0:+,1:+,2:~];
	FROM_EQ_ENVFROM(0.00)[];
	ASN(0.00)[asn:25577, ipnet:84.45.0.0/17, country:GB];
	MLMMJ_DEST(0.00)[questions@freebsd.org];
	DMARC_NA(0.00)[fjl.co.uk];
	RCPT_COUNT_ONE(0.00)[1];
	FROM_HAS_DN(0.00)[];
	MID_RHS_MATCH_FROM(0.00)[];
	TO_MATCH_ENVRCPT_ALL(0.00)[];
	TO_DN_NONE(0.00)[];
	PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org];
	ARC_NA(0.00)[]
X-Rspamd-Queue-Id: 4Sn5LJ3h0Cz4Yy6
X-Spamd-Bar: +

This is a multi-part message in MIME format.
--------------bIp731yCGNeEXNbHAbVNoBvm
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

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 :-(

--------------bIp731yCGNeEXNbHAbVNoBvm
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 08/12/2023 19:21, <a
        class="moz-txt-link-abbreviated moz-txt-link-freetext"
        href="mailto:robert@rrbrussell.com" moz-do-not-send="true">robert@rrbrussell.com</a>
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:a85d66a9-528a-4b90-ac4b-a204009da334@app.fastmail.com">
      <pre class="moz-quote-pre" wrap="">On Fri, Dec 8, 2023, at 12:43, Frank Leonhardt wrote:
</pre>
      <blockquote type="cite">
        <pre class="moz-quote-pre" wrap="">&lt;snip&gt;
I got "bad vibes" going to from 13.2-&gt;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"'
&lt;snip&gt;

Has anyone else had the same problem, and what are the runes to avoid it 
should I decide to have another go?
&lt;snip&gt;
</pre>
      </blockquote>
      <pre class="moz-quote-pre" wrap="">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.

</pre>
    </blockquote>
    <p>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.
      <span style="white-space: pre-wrap">Good idea to use pkg-static to recover pkg, but </span>I
      took this as a bad sign and did a rollback. I suspect there was
      more than just this wonky about it.<span
      style="white-space: pre-wrap"> The certificate login was also broken, and I'm sure csh being swapped out would cause trouble too :-(</span></p>
    <p><span style="white-space: pre-wrap">
</span></p>
    <p><span style="white-space: pre-wrap">
</span></p>
  </body>
</html>

--------------bIp731yCGNeEXNbHAbVNoBvm--