Re: current amd64 snapshot 20250807 pkgbase installation seems broken

Kyle Evans <kevans_at_FreeBSD.org> wrote on
Date: Sun, 10 Aug 2025 04:12:32 UTC :

> On 8/9/25 23:08, cyric@mm.st wrote:
> > tetrosalame wrote:
> >> Hi current@,
> >>
> >> since last days churn about pros and cons of pkgbase, I downloaded
> >> 20250807 amd64 snapshot to discover what's all this thing is about :)
> >> It's been a while since I last used bsdinstall, I'm more a untar base
> >> tarball guy.
> >> BTW I chose pkgbase experimental installation, ZFS autoconf, set up
> >> network (while here, how do I configure HTTP(S)_PROXY please? I think
> >> that would be my next stopper...) and pkg didn't run.
> >> Console says (ALT-F4):
> >> ld-els.so.1: Shared object "libutil.so.9" not found, required by "pkg"
> > 
> > Not really a snapshot problem, packages aren't rebuilt yet to utilize
> > libutil.so.10 (same problem here). Once it's done, just use pkg-static.
> > 
> >> 20250801 snapshot works as intended, but I'm stuck anyway as I can't
> >> find a way to tell pkg to use my local proxy.
> >>
> >> Am I doing something wrong?
> > P.S. https://pkg-status.freebsd.org/?all=1 says last main-amd64 build is
> > still running since Aug 5, something broken here?
> > 
> 
> If you click on the bomb icon, it'll take you into the per-builder page 
> that shows you what's going on -- it's still actively building, and
> still has some ~14k ports remaining to build.

beefy18's (main-amd64's port-package builder) is currently
based on:

Host OSVERSION: 1500052
Jail OSVERSION: 1500056

from back on 2025-Aug-05.

But:  libcrypto.so <http://libcrypto.so/>.35 (which is needed for main now) is from 2025-Aug-07 in its Makefile.
Also: libssl.so <http://libssl.so/>.35    (which is needed for main now) is from 2025-Aug-07 in its Makefile.

So /usr/local/sbin/pkg will still depend on
libssl.so.30 and libcrypto.so.30 when the
next main-amd64 port-pacakge updates are
distributed.

(libutil.so <http://libutil.so/>.10 is older: it is in the 2025-Aug-02 Makefile.)

So pkg will still not be working for main when
the current beefy18 build completes and is
distributed, as understand things.

===
Mark Millard
marklmi at yahoo.com