Re: source upgrade of OS leaves pkg using pkg.freebsd.org non-functional

oid <void_at_f-m.fm> wrote on
Date: Tue, 09 Sep 2025 17:31:52 UTC :

> On Tue, Sep 09, 2025 at 06:27:35PM +0100, Lexi Winter wrote:
> 
> >yes: ports packages are not available for 16 yet, so you'll have to
> >build from source for now.
> 
> ok, thanks for confirming

Going along with that is that, while,

https://pkg.FreeBSD.org/FreeBSD:16:amd64/

(or other such?) does exist just recently,

https://pkg.freebsd.org/FreeBSD:16:amd64/kmods_latest/
and:
https://pkg.freebsd.org/FreeBSD:16:amd64/latest/

still have not been created (as of when I looked).

https://pkg.freebsd.org/FreeBSD:16:aarch64/

is still: "404 Not Found"

as well (as of when I looked).

But things are in process and you can monitor
such places that happen to be of interest.


Other notes:

If pkg 2.3.0 ends up being released soon enough,
stopping:

https://pkg-status.freebsd.org/beefy18/build.html?mastername=main-amd64-default&build=p118fb2971704_s4ab64e34911
(or other such main-* builds)

and running a build based on pkg 2.3.0 may well
take noticable less overall time than letting
the pkg 2.2.2 based build of main-amd64
port-packkages continue.

(pkg 2.[12].* and main-*'s debug poudriere jail
combination makes the builds take a very long
time: 240+ Hrs to 480+ Hrs for beefy18 when most
everything is being rebuilt. ampere2 for aarch64
takes longer.)

===
Mark Millard
marklmi at yahoo.com