Date: Fri, 8 Dec 2023 22:25:21 +0000 From: Frank Leonhardt <freebsd-doc@fjl.co.uk> To: questions@freebsd.org Subject: Re: pkg killed on FreeBSD upgrade to 14 Message-ID: <1ba6fb31-9a43-47fa-aa0e-721e179c7317@fjl.co.uk> In-Reply-To: <a85d66a9-528a-4b90-ac4b-a204009da334@app.fastmail.com> References: <d990e8a3-e84f-4965-95bf-f3abf21ac96f@fjl.co.uk> <a85d66a9-528a-4b90-ac4b-a204009da334@app.fastmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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=""><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>
</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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1ba6fb31-9a43-47fa-aa0e-721e179c7317>