[Bug 288817] Recent FreeBSD 15.0-CURRENT images in GCP are broken with Cirrus CI

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288817

Mark Millard <marklmi26-fbsd@yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marklmi26-fbsd@yahoo.com

--- Comment #1 from Mark Millard <marklmi26-fbsd@yahoo.com> ---
For main-* (beefy18, beefy17, ampere2), I
expect that the timing of:

        libutil.so.9 => not found (0)
/lib/libutil.so.10

vs. also having (later):

        libssl.so.30 => not found (0)
        libcrypto.so.30 => not found (0)
/lib/libcrypto.so.35
/usr/lib/libssl.so.35

at issue.

Some port-package builders are running poudriere
jail worlds with /lib/libutil.so.10 now and have
even completed builds with such if I remember
right.

But none are yet running such worlds with:
/lib/libcrypto.so.35 or /usr/lib/libssl.so.35


Notes about the timing of availability as stands:

The main-* port-package build servers are:

main-amd64: beefy18
main-i386:  beefy17 (Unsure when i386 will having main built!)
main-arm64: ampere2
main-armv7: ampere2 (yes: again)

(I do not have details for distribution stage or servers.)

These notes based on recent times with pkg 2.2.1 or
pkg 2.2.2 in use on the builders in question.

There is also the timing of the ports-tree snapshot
involved. Some combinations will not match the
staging for the above well.


What is needed for main-* follow. Notes were originally
typed early on 2025-Aug-12 UTC but are only intended to
give ball park figures.


The poudriere Jails need to have a 2025-Aug-12+ (UTC) or so
Jail OSVERSION that is 1500059 (or later)

The poudriere Jails needs to be using a ports tree from
2025-Aug-12+ (UTC) or so

No existing build activity is that recent.



main-amd64 on beefy18: 2025-Aug-26 or so

Details . . .

Jail OSVERSION is currently at: 1500056

It takes 250 Hrs to 270 Hrs or so to build an update in recent times.
So about 10 to 11 Days.

The existing build has about 100 Hrs to go (about 4 days).
Then the jail osversion and ports tree can be updated.

So 4 days + 10 days +  ? days is: 14 days+



main-i386 on beefy17: 2025-Aug-26 or so

Details . . .

Jail OSVERSION is currently at: 1500056

It takes 245 Hrs to 260 Hrs or so to build an update in recent times.
So also about 10 to 11 Days.

The existing build has about 90 Hrs to go (about 4 days).
Then the jail osversion and ports tree can be updated.

So 4 days + 10 days +  ? days is: 14 days+




ampere 2 cycles between building main-aarch64 and main-armv7 .

So things are more complicated and sequential.

main-arm64 on ampere2: 2025-Sep-07 or so
main-armv7 on ampere2: 2025-Sep-23 or so

Details . . .

Jail OSVERSION is currently at: 1500052

main-armv7 is building currently.

main-armv7 takes 390 Hrs to 420 Hrs to build.
So about 16 days to 18 days.

The existing build has about 230 Hrs to go (about 10 days).
Then the jail osversion and ports tree can be updated.

main-arm64 takes 390 Hrs to 420 Hrs to build.
So about 16 days to 18 days.
So 10 days + 16 days + ? days is: 26 days+

main-armv7 takes 390 Hrs to 420 Hrs to build.
So about 16 days to 18 days.
So 26 days + 16 days + ? days is: 42 days+

-- 
You are receiving this mail because:
You are the assignee for the bug.