Re: No packages lately for arm64?

From: Carl Johnson <carlj_at_peak.org>
Date: Mon, 17 Jul 2023 21:35:36 UTC
Mark Millard <marklmi@yahoo.com> writes:

> On Jul 17, 2023, at 08:50, Carl Johnson <carlj@peak.org> wrote:
>
>> Hello,
>> I have been watching for packages for the new quarterly port builds, but
>> I haven't seen anything yet.  I already update my amd64 system several
>> days ago, but nothing has shown yet for arm64.  I checked my logs and I
>> installed security updates last month, but there haven't been any for
>> the last couple of weeks.  When I run pkg update, I just get the
>> following:
>> 
>>    # pkg update
>>    Updating FreeBSD repository catalogue...
>>    FreeBSD repository is up to date.
>>    All repositories are up to date.
>> 
>> I have compared some package versions to my amd64 system and the arm64
>> packages are definitely out of date.  I am running FreeBSD 13.2-RELEASE
>> and all pkg configuration files are the original defaults.  Is there
>> some web site I could look at to see the build status for packages?
>
> There were major problems with pkg and its performance and resource
> use in an update. Official builds for latest were stopped and
> restarted multiple times as pkg was updated to try to get past the
> issues.
>
> On 2023-Jul-13 9 builds were started, each on a separate server, each
> with 25000+ ports to build. None were quarterly.  Looks like 3
> are still not done, one being for arm64 on ampere2. The other of
> the 9 build servers are off doing other builds now. 131releng-armv7
> started building on ampere3 but is not quarterly. It has 26000+ ports
> to build.
>
> But 131arm64's quarterly is building on ampere1 and has 12000+ of
> 25000+ to go.
>
> These notes do not cover distribution of built packages to the
> distribution servers. That adds more time after the builds and
> the status is not as easy to find.
>
> I used https://pkg-status.freebsd.org/?all=1&type=package to gather
> some of the details presented.

Mark,
Thanks for the information.  I have bookmarked that so I can look it up
myself in the future.

-- 
Carl Johnson		carlj@peak.org