Re: WARNING: looks like main-amd64-default (latest) will only have 519 port-packages distributed for 11+ days [main-arm64 in process now too, only 514 for 16+ days]
- Reply: Mark Millard : "Re: WARNING: looks like main-amd64-default (latest) will only have 519 port-packages distributed for 11+ days [main-arm64 in process now too, only 514 for 16+ days]"
- In reply to: Mark Millard : "Re: WARNING: looks like main-amd64-default (latest) will only have 519 port-packages distributed for 11+ days [main-arm64 in process now too, only 514 for 16+ days]"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 19 Aug 2025 04:57:21 UTC
On Aug 17, 2025, at 17:51, Mark Millard <marklmi@yahoo.com> wrote: > On Aug 17, 2025, at 08:49, Mark Millard <marklmi@yahoo.com> wrote: > >> https://pkg-status.freebsd.org/beefy18/build.html?mastername=main-amd64-default&build=p98b748365fe6_sc6778f3a442 >> >> shows that a special build of main-amd64-default (latest) has >> happened as a part of dealing with changes associated with >> 15.0-PRERLEASE status. >> >> It is a from-scratch build that has established: >> >> Host OSVERSION: 1500061 >> Jail OSVERSION: 1500061 >> >> which is after some library .so.* version number changes. >> Prior to this build, the distributed pkg builds were too old >> for main-amd64's 15.0-PRERELEASE . >> >> Only 40 packages were explicitly listed/requested and those >> lead to only 519 packages being built. beefy18 is the system >> used for main-amd64 port-package builds. >> >> beefy 18 has been taking 260 Hrs to 270 Hrs to build a full >> set of packages. Getting copies to the distribution servers >> around the world is a separate step I do not have time >> frames for. >> >> So: around 11+ days --once beefy18's full/normal builds are >> started-- before a full set of port-packages will be >> available. > > FYI: > > ampere2 (builds main-arm64 and main-armv7) activity was stopped > and it is now doing a similar main-arm64 build: 40 requested, > queued 514, 2 ignored. Still in process, with no failures so > far. > > Full main-arm64 builds take more like 400 Hrs, so 16 days > or more. Presuming that main-arm64 is full-built before > main-armv7 . . . > > Looks like main-arm64 will have only 514 port packages > distributed for 16+ days once the special, small build has > finished and is distributed. > > The build may have to be redone because it is based on > f9ff1e48cc1, which has been reverted for debug-kernel > panics from an incorrect assert when using nfs mounted > file systems. main-armv7 is being built with 36995 queued and 1747 ignored, and 776 initially skipped. So 34472 port package builds to be attempted before main-arm64 starts. main-armv7: 16+ days main-arm64: 16+ days So: 31+ days for a fully-populated main-arm64 to become available. === Mark Millard marklmi at yahoo.com