Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Dec 2023 18:54:13 +1100
From:      Dewayne Geraghty <dewayne@heuristicsystems.com.au>
To:        questions@freebsd.org, freebsd-doc@fjl.co.uk
Subject:   Re: pkg killed on FreeBSD upgrade to 14
Message-ID:  <f187d486-72a8-40da-8815-506edd2b4d69@heuristicsystems.com.au>
In-Reply-To: <1ba6fb31-9a43-47fa-aa0e-721e179c7317@fjl.co.uk>
References:  <d990e8a3-e84f-4965-95bf-f3abf21ac96f@fjl.co.uk> <a85d66a9-528a-4b90-ac4b-a204009da334@app.fastmail.com> <1ba6fb31-9a43-47fa-aa0e-721e179c7317@fjl.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------c7qQQPES0triLZQT4WMl0Cig
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 9/12/2023 9:25 am, 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 :-(
>
Frank,

I avoid major version upgrades and performed a fresh 14.0 install.  Then 
attempted to git clone releng/14.0 due to the errata notices.  
Unfortunately neither git (GPLv2) nor got (ISCL) are included.  So, like 
curl and fetch, I set the environment variables HTTPS_PROXY and 
HTTP_PROXY and attempted to use pkg. Only much later did I realise (man 
pkg.conf Examples) that I needed to set these variables somewhere within 
pkg.conf. ie pkg didn't fail so we can compare.

Anyway to your specifics.  My FreeBSD14.0R install has
/usr/lib/libssl.so.30
while my BSD 13.2S has
/usr/lib/libssl.so.111

I strongly suspect that either your upgrade has become muddled or you're 
using the ports version of pkg.  Check your search path for pkg with

which pkg
it should return
/usr/sbin/pkg
if it returns /usr/local/sbin/pkg then you are using the ports software, 
which remains linked to libssl.so.111.  The other clue is that 
pkg-static isn't in the base FreeBSD14.0 :)

Aside: I can't speak for poudriere being more reliable as portmaster has 
serverd me very well, but I value predictability and simplicity ;)

--------------c7qQQPES0triLZQT4WMl0Cig
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 9/12/2023 9:25 am, Frank Leonhardt
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:1ba6fb31-9a43-47fa-aa0e-721e179c7317@fjl.co.uk">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <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>
    </blockquote>
    <p>Frank,</p>
    <p>I avoid major version upgrades and performed a fresh 14.0
      install.  Then attempted to git clone releng/14.0 due to the
      errata notices.  Unfortunately neither git (GPLv2) nor got (ISCL)
      are included.  So, like curl and fetch, I set the environment
      variables HTTPS_PROXY and HTTP_PROXY and attempted to use pkg.  
      Only much later did I realise (man pkg.conf Examples) that I
      needed to set these variables somewhere within pkg.conf. ie pkg
      didn't fail so we can compare.<br>
    </p>
    <p>Anyway to your specifics.  My FreeBSD14.0R install has <br>
      /usr/lib/libssl.so.30 <br>
      while my BSD 13.2S has<br>
      /usr/lib/libssl.so.111<br>
    </p>
    <p>I strongly suspect that either your upgrade has become muddled or
      you're using the ports version of pkg.  Check your search path for
      pkg with </p>
    <p>which pkg<br>
      it should return<br>
      /usr/sbin/pkg<br>
      if it returns /usr/local/sbin/pkg then you are using the ports
      software, which remains linked to libssl.so.111.  The other clue
      is that pkg-static isn't in the base FreeBSD14.0 :)<br>
    </p>
    <p><span style="white-space: pre-wrap">Aside: I can't speak for poudriere being more reliable as portmaster has serverd me very well, but I value predictability and simplicity ;)</span></p>
    <p><span style="white-space: pre-wrap">
</span></p>
    <blockquote type="cite"
      cite="mid:1ba6fb31-9a43-47fa-aa0e-721e179c7317@fjl.co.uk"> </blockquote>
  </body>
</html>

--------------c7qQQPES0triLZQT4WMl0Cig--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f187d486-72a8-40da-8815-506edd2b4d69>