RE: https://portsfallout.com/ doesn't seem to show all fallout

Yuri <yuri_at_FreeBSD.org> wrote on
Date: Sun, 21 Apr 2024 21:16:48 UTC :

> For example, I've got a fallout message for 133amd64 for misc/py-mmcv, 
> but https://portsfallout.com/ shows zero fallout for this port, when 
> searched by port origin.


The  search field at https://pkg-status.freebsd.org/?all=1&type=package with "133a" in it finds no matches. But "132a" finds "132amd64" Jail references.

Also: It is 3 months or so after 13.3 before the builders are switched to be using 13.3 for building the public-server's packages (instead of 13.2).

My guess here is that you are getting fallout notices from non-public builder experiments being done in preparing for later public use of 13.3 .

To my knowledge, https://portsfallout.com/ only covers the public package build activity, not internal/non-public experiments. This goes along with https://portsfallout.com/server showing no examples of "133" but showing examples of "build environment" names that contain "132". That property matches the https://pkg-status.freebsd.org/?all=1&type=package results.

===
Mark Millard
marklmi at yahoo.com