Re: package build status for 14.x arm64 release

On Aug 20, 2025, at 05:08, 風來散人 <[email protected]> wrote:

> I don't see any 14.3 arm64 package status on https://pkg-status.freebsd.org/. There are 2 14.2 arm64 (default and quarterly) but they had been built on July (more than 1 months ago).
> Does anybody know what is the problem?

First answer:

14.3 does not start to be used for building port-packages
until 14.2 goes EOL. Until then, 14.2 port-packages are
used on 14.3 systems (that get port-packages from official
FreeBSD distribution servers).

Second answer:

ampere3 builds 4 different types of "latest" builds in a
cycle:

135arm64-default
135releng-armv7-default
142arm64-default
142releng-armv7-default

The cycle that started at:

Tue, 08 Jul 2025 03:07:25 GMT

was followed by a cycle that started at:

Tue, 05 Aug 2025 03:24:10 GMT

So sometimes the cycle can take almost a month for aarch64
and armv7 latest, in this case somewhat closer to 4 weeks.

Another contributing factor is that the ports tree used
is only updated at the beginning of the cycle, not between
each step in the cycle. Thus the ports tree update took
about a month for the above example.


Note: the ampere1 referenced below has been crashing
fairly frequently. That also contributes to the time
frames involved. But it also means that I'll not
give example times for a cycle. 142amd64-quarterly is
working on its 5th attempt to build. The first attempt
started at Tue, 05 Aug 2025 03:12:41 GMT.

ampere1 builds 4 different types of "quarterly" builds in
a cycle:

142arm64-quarterly
135arm64-quarterly
135releng-armv7-quarterly
142releng-armv7-quarterly

Another contributing factor is that the ports tree used
is only updated at the beginning of the cycle, not between
each step in the cycle.


By contrast, amd64/i386 has 1 builder machine for each type
of build. So the cycle-length is always 1, not 4 (as above)
or 2 (ampere2 for main-arm64 and main-armv7).


===
Mark Millard
marklmi at yahoo.com