09.08.2024 23:02, Theo Buehler пишет:
> This went through an amd64 bulk with no fallout. Since it doesn't build
> on sparc64 and has protobuf as a consumer, sparc64 won't be happy, but
> it hasn't been in a happy place for a while.

I'll give fixing the sparc64 build a try and hold off with the update,
although not for too longas I don't think sparc64 should block the other archs.

> How do you intend to deal with the inevitable wantlib churn?

For a previous update I went over some (most?) consumers and synced WANTLIB
as needed, but that was required as abseil dropped some libs.

Now it just adds some, out-of-sync will still build -- If there's some bulk
log that already contains pointers as to which ports need syncing, I'll can
sieve through them.