Re: Packages not build for arm64/aarch64 [it has recently been roughly a month between updates for a given type of aarch64 build]

Just an FYI to Jack Raats:

Your Email environment rejected my Email as:

QUOTE (but edited for _at_)
554: 5.7.1 <marklmi_at_yahoo.com>: Sender address rejected: You are a spammer
END QUOTE

so any more from me will just be on-list, no direct copy
to your Email address.

Mark

On Jul 14, 2025, at 13:38, Mark Millard <[email protected]> wrote:

> Jack Raats <mlist_at_jarasoft.net> wrote on
> Date: Mon, 14 Jul 2025 18:07:01 UTC :
> 
>> Perhaps this is not the right mailinglist to ask this question, excusez moi.
>> 
>> Are the packages (latest) for arm64.aarch64 not being build the last 4 weeks?
> 
> As things are right now with pkg 2.2.1 in use, the detailed
> answers are very different between main [so: 15] vs. 14.2/13.5.
> The quick summary is: recently it has been about a month
> between package builds completing for a given type of
> aarch64 or armv7 context.
> 
> Details follow in case you care.
> 
> 
> main-arm64/main-armv7 built on ampere2:
> (main [so: 15 as stands] is always latest, not quarterly)
> 
> As stands, the build machine ampere2 cycles between building
> main-arm64 and main-armv7, each of those 2 taking around
> 2 weeks or somewhat more, totaling a round a month or more.
> Part of this is the interval is long enough that generally
> the build is a (nearly) full build instead of a more
> noticeably smaller incremental build.
> 
> The last 2 build start times and end dates
> for main-arm64 are:
> 
> Tue, 06 May 2025 02:47:25 GMT ending during May-26
> . . . main-armv7 built here . . .
> Sat, 14 Jun 2025 02:48:40 GMT ending during Jun-30
> 
> (Note: The above does not explicitly show time for
> distribution of the updates around the world.)
> 
> So, more than a month for the interval between builds
> finishing.
> 
> No main-arm64/main-armv7 builds have started using pkg
> 2.2+ yet. The next to start should be using pkg 2.2.1 .
> 
> pkg 2.2.1 usage in future builds should help with this
> some, but not greatly, an issue unique to main-* .
> 
> 
> 142arm64/142releng-armv7/135arm64/143releng-armv7 on ampere3
> (these are all latest: ampere1 deals with quarterly)
> 
> As stands, the build machine ampere3 cycles between building
> each of the 4 types of latest build. Individually these
> builds do not take as long as the main-* ones do. But there
> are 4 builds in the cycle instead of 2 builds.
> 
> But, these builds do do not take nearly as long and manage to
> commonly be somewhat more incremental from one to the next as
> well, more often than the main-* ones do.
> 
> Using 142arm64 as the cycle boundary example sequence,
> incremental builds involved:
> 
> Fri, 30 May 2025 17:00:08 GMT ended during Jun-8
> . . . 3 other types of builds, then: . . .
> Thu, 26 Jun 2025 13:06:30 GMT ended during Jul-8
> 
> (Note: The above does not explicitly show time for
> distribution of the updates around the world.)
> 
> So, about a month for the interval between
> 142arm64 builds completing, despite 4 types of
> builds being done in a cycle.
> 
> The first pkg 2.2+ based build (135arm64 using
> pkg 2.2.1) started on Tue, 08 Jul 2025 03:07:25 GMT
> and has under 4000 packages to go.
> 
> Unlike for main-*, the pkg 2.2.1 usage should be a
> far more noticeable improvement vs. when pkg 2.1.*
> was in use. But it is going to be a while before a
> full cycle of updates using 2.2.1 has completed
> in order to have measurements.



===
Mark Millard
marklmi at yahoo.com