Bug 286591 - PKG index for ARM64 seams do be out of date
Summary: PKG index for ARM64 seams do be out of date
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Package Infrastructure (show other bugs)
Version: Latest
Hardware: arm64 Any
: --- Affects Many People
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-05 05:25 UTC by schmidt
Modified: 2025-05-16 05:49 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description schmidt 2025-05-05 05:25:44 UTC
I'm running FreeBSD 14.2 on a ARM64 Machine. I also have a FreeBSD 13.4 Machine running on AMD64.  

I update the installed packages on both machines at the same time regularly. Some time now only the AMD64 machine gets updates. The ARM64 version claims no new updates are there. 

That's wrong. The pkg package itself is outdated. On AMD64 i installed version 2.1.2 today while the ARM64 machine claims that 1.21.3 is the current version. 

[root@midgard ~]# pkg upgrade -f pkg 
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:
        pkg-1.21.3

Number of packages to be reinstalled: 1

Proceed with this action? [y/N]: y
[1/1] Reinstalling pkg-1.21.3...
[1/1] Extracting pkg-1.21.3: 100%

What I'm doing wrong or is there a problem with the ARM64 pkg repository

Regards 
   Estartu
Comment 1 schmidt 2025-05-10 06:43:22 UTC
It seams that the pkg repository of aarch64 is not updated. 

the newest file in https://pkg.freebsd.org/FreeBSD:14:aarch64/quarterly/ is from 
March 31. 2025

That's around the time when updates on my arm64 machine stopped
Comment 2 schmidt 2025-05-10 06:45:40 UTC
The newest file in https://pkg.freebsd.org/FreeBSD:14:amd64/quarterly/
if from Mai 8. 2025.
Comment 3 schmidt 2025-05-10 06:48:39 UTC
https://pkg.freebsd.org/FreeBSD:13:aarch64/quarterly/ has the current files.
Comment 4 Mark Millard 2025-05-16 01:11:57 UTC
Looking at https://pkg-status.freebsd.org/builds?type=package&all=1
with appropriate searches and sorting shows:

142arm64's quarterly started building on
Sat, 10 May 2025 03:10:18 GMT and still
has 6716 to go, having built 28212 so far
in 141:14:58 . The prior analogous, but
much smaller (incemental) build,
was for 141arm64 and started on
Sat, 29 Mar 2025 05:35:24 GMT taking
50:28:17 .


One issue is that as of pkg 2.1.0+ being
involved, the (nearly) from-scratch builds 
take somewhat longer compared to when pkg
2.0.6 or before was involved. The
arm64/armv7 systems (ampere*) are not
the faster systems.

Another is that ampere1 cycles through
building 4 distinct build types (arm64/armv7
combined with 14.2/13.4), unlike amd64
systems that build just one type each and
the next build is of the same type. (There
are far more amd64/i386 systems.)

A result of both of the above is that a
build cycle of the 4 builds can take much
of a month to complete and start the next
cycle, at least when the cycle has large
numbers of build to do for each type.
No so long when they happen to be small
incremental builds instead. (Quarterly
gets such smaller builds far more often.)

Another issue is that ampere1 has been
crashing a lot in recent times. (Cause
unknown as far as I know.) There were 4
crashes in April and 1 sigterm so far in
May. The crashes insert delays.

Do not expect arm64 and amd64 to be
synchronized. If the 6716 finish without
a crash, there should finally be a 142arm64
quarterly update, one that would include
pkg 2.1.2 .
Comment 5 Ronald Klop freebsd_committer freebsd_triage 2025-05-16 05:49:25 UTC
I made a graph to quickly see the age of a pkg repo.

https://www.klop.ws/pkgstats/pkg-age.html

It shows what Mark says. Arm (red/orange) is always behind on Intel/AMD (blue/green).
Q2 starting in the beginning of April was a slow start for both architectures, and Intel/Amd recovered more quickly. 

Cheers.