From nobody Mon Dec 11 07:54:13 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 4SpYtV6RNCz53B0M for ; Mon, 11 Dec 2023 07:54:42 +0000 (UTC) (envelope-from dewayne@heuristicsystems.com.au) Received: from heuristicsystems.com.au (hermes.heuristicsystems.com.au [203.41.22.115]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2560 bits) client-digest SHA256) (Client CN "hermes.heuristicsystems.com.au", Issuer "Heuristic Systems Type 4 Host CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SpYtS10DDz4M8B for ; Mon, 11 Dec 2023 07:54:39 +0000 (UTC) (envelope-from dewayne@heuristicsystems.com.au) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=heuristicsystems.com.au header.s=hsa header.b=TkmhMnQl; spf=pass (mx1.freebsd.org: domain of dewayne@heuristicsystems.com.au designates 203.41.22.115 as permitted sender) smtp.mailfrom=dewayne@heuristicsystems.com.au; dmarc=none Received: from [10.0.5.4] ([10.0.5.4]) (authenticated bits=0) by heuristicsystems.com.au (8.15.2/8.15.2) with ESMTPA id 3BB7sDhN056574; Mon, 11 Dec 2023 18:54:17 +1100 (AEDT) (envelope-from dewayne@heuristicsystems.com.au) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=heuristicsystems.com.au; s=hsa; t=1702281259; x=1702886060; bh=O2RvumPC8/wUgAPlEnRN8GFn328MoAu4nuCplPCCuvs=; h=Message-ID:Date:Subject:To:From; b=TkmhMnQlv7vM5YFkucUTfSoJ3cY/y/U2joWmka4dFqqXCaxgzfgElI2nQsFQR5th2 6H6fm0ze/ITkd5nfHYj7VuzgMnpLJZtrgi5XUx6CKWzrNAdWWE0dgs0wYGU2lzE7fU hpCfAK2UflBTgJAq0k5DtoWdtf4oulDug69g4WETptXe7INRyc1W9 Content-Type: multipart/alternative; boundary="------------c7qQQPES0triLZQT4WMl0Cig" Message-ID: Date: Mon, 11 Dec 2023 18:54:13 +1100 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: pkg killed on FreeBSD upgrade to 14 Content-Language: en-GB To: questions@freebsd.org, freebsd-doc@fjl.co.uk References: <1ba6fb31-9a43-47fa-aa0e-721e179c7317@fjl.co.uk> From: Dewayne Geraghty In-Reply-To: <1ba6fb31-9a43-47fa-aa0e-721e179c7317@fjl.co.uk> X-Spamd-Result: default: False [-6.01 / 15.00]; DWL_DNSWL_MED(-2.00)[heuristicsystems.com.au:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.92)[-0.924]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[heuristicsystems.com.au:s=hsa]; RCVD_IN_DNSWL_MED(-0.20)[203.41.22.115:from]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; XM_UA_NO_VERSION(0.01)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[heuristicsystems.com.au]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:1221, ipnet:203.40.0.0/13, country:AU]; DKIM_TRACE(0.00)[heuristicsystems.com.au:+]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org] X-Rspamd-Queue-Id: 4SpYtS10DDz4M8B X-Spamd-Bar: ------ 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: >>> >>> 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"' >>> >>> >>> Has anyone else had the same problem, and what are the runes to avoid it >>> should I decide to have another go? >>> >> 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
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--