On Apr 17, 2025, at 02:20, Baptiste Daroussin <b...@freebsd.org> wrote:
> On Wed 16 Apr 22:39, Baptiste Daroussin wrote:
>> On Wed 16 Apr 13:24, Mark Millard wrote:
>>>
>>>
>>> ===> Installing existing package /packages/All/glib-bootstrap-2.84.1,2.pkg
>>> [aarch64PBase] Installing glib-bootstrap-2.84.1,2...
>>> [aarch64PBase] `-- Installing libiconv-1.17_1...
>>> [aarch64PBase] `-- Extracting libiconv-1.17_1: .......... done
>>> [aarch64PBase] `-- Installing libinotify-20240724...
>>> [aarch64PBase] `-- Extracting libinotify-20240724: .......... done
>>> [aarch64PBase] `-- Installing pcre2-10.45...
>>> [aarch64PBase] `-- Extracting pcre2-10.45: .......... done
>>> [aarch64PBase] `-- Installing py311-packaging-24.2...
>>> [aarch64PBase] `-- Extracting py311-packaging-24.2: .......... done
>>
>> Thanks I'll dig into it.
>
> Fixed! in pkg 2.1.99.2 (but you will have to rebuild some packages from
> scratch
> (in your case glib-bootstrap for sure needs to be rebuilt;
The rebuild worked: no problems with glib-bootstrap
during the build of www/gitlab@ee .
However, I no longer have a (nearly) full "bulk -a"
result:
. . .
[00:00:14] -C specified, cleaning listed packages
[00:00:14] (-C) Flushing package deletions
[00:00:14] Trimming IGNORED and blacklisted ports
[00:00:14] pkg bootstrap missing: unable to inspect existing packages, cleaning
all packages... done
. . .
[01:52:51] [release-aarch64-alt] [2025-04-17_12h27m16s] [committing] Time:
01:52:41
Queued: 1252 Inspected: 0 Ignored: 0 Built: 1252 Failed: 0 Skipped:
0 Fetched: 0 Remaining: 0
[01:52:51] Logs:
/usr/local/poudriere/data/logs/bulk/release-aarch64-alt/2025-04-17_12h27m16s
. . .
Only those 1252 packages are present:
# ls -loaTt /usr/local/poudriere/data/packages/release-aarch64-alt/All/ | grep
'pkg$' | wc -l
I guess my means of causing rebuilds of the recent builds
was not a good idea. I no longer have 34K+ local packages
already built.
As having a huge collection of packages already built had
seemed to contribute to the time frames for builds involving
pkg 2.1.0, I no longer have a great test context for what
a "bulk -c -a" might like unless I do another one from
scratch. Such would take 60+ hours based on pre 2.1.0
experience, so more than 3 days to establish the context
for non-parallel timing experiments.
Some previous testing suggested pkg-2.1.99.1.pkg did well
when the huge number of locally built packages were
already present. But that involved the problem that
pkg-2.1.99.2.pkg fixed as well.
===
Mark Millard
marklmi at yahoo.com
