Re: ampere2 and 15.0-PRERELEASE with pkg 2.2.2 for main-arm64 and main-armv7 : the last build is almost done [15stable-arm64 is building on ampere2]

On Sep 26, 2025, at 07:51, Mark Millard <marklmi@yahoo.com> wrote:

> On Sep 26, 2025, at 01:01, Ronald Klop <ronald-lists@klop.ws> wrote:
> 
>> Hi,
>> 
>> Does anybody know on what machine the new 15arm64 builds will be running? As that will give another long running build on these machines which are already under pressure. I really hope there will be a new machine available for this.

See:

https://pkg-status.freebsd.org/ampere2/build.html?mastername=15stable-arm64-default&build=53919f5dd30e

It is 15stable-arm64-default (arm64 latest's port packages)
being built on ampere2 .

Looks like builds of main-arm64 and main-armv7 port-packages
are canceled for now. (The 15.0-RELELASE process likely can
not afford to wait for either of the others to be in a cycle
that would force long periods between 15.0-* builds.)

(But it trades off doing the type of testing that building
port-packages for main involves.)


> Tier 1 requires (quoting):
> 
>    • Official binary packages for third party software will be
> provided by the ports team. For embedded architectures, these
> packages may be cross-built from a different architecture.
> 
>    • Dedicated hardware in one of the FreeBSD clusters for
> package building (either natively or via qemu-user).
> 
>    • Developers should be able to build packages on commonly
> available, non-embedded Tier 1 systems. This can mean either
> native builds if non-embedded systems are commonly available
> for the platform in question, or it can mean cross-builds 
> hosted on some other Tier 1 architecture.
> 
> 
> Tier 2 does not. But (quoting):
> 
>    • The ports infrastructure should include basic support
> for Tier 2 architectures sufficient to support building ports
> and packages. This includes support for basic packages such
> as ports-mgmt/pkg, but there is no guarantee that arbitrary
> ports will be buildable or functional.
> 
>    • Tier 2 platforms should be self-hosting either via the
> in-tree toolchain or an external toolchain. If an external
> toolchain is required, official binary packages for an external
> toolchain will be provided.
> 
> 
> So: no claim of Official binary packages for general 3rd party
> software.
> 
> 
> armv7 is Tier 2 for All Supported Platforms (13.*, 14.*, and
> upcoming 15.*). Technically FreeBSD could choose to not do as
> many types (or any types) of armv7 builds for a time. Or they
> could go back to trying to use qemu on amd64 for targeting armv7
> for a time for at least some types of builds. (As I remember,
> the qemu armv6 builds were only able to build a few thousand
> ports towards the end of the armv6 official builds time frame.)
> Or adding new builder machines. Or just adding to the work load
> on the existing builder machines, still doing some or all of
> the armv7 builds.
> 
> It will be interesting to see what is done.
> 
> Mark
> 
>> Regards,
>> Ronald.
>> 
>> Van: Mark Millard <marklmi@yahoo.com>
>> Datum: vrijdag, 26 september 2025 07:48
>> Aan: FreeBSD-pkg@freebsd.org
>> Onderwerp: ampere2 and 15.0-PRERELEASE with pkg 2.2.2 for main-arm64 and main-armv7 : the last build is almost done (It is a main-armv7 build)
>> The port-package builds are done and ampere2 is doing the
>> "clean_restricted:" and "pkgrepo:" sorts of final stages
>> before distribution servers around the world are updated.
>> 
>> The next build by ampere2 should be based on pkg 2.3.1
>> (or later) and take less time, even if the number of
>> port-package builds is the same.
>> 
>> Hopefully the jail worlds will be updated to 160000+
>> based before the next build starts.
>> 


===
Mark Millard
marklmi at yahoo.com