@dch from that issue, it's still unclear as to the exact cause of the package metadata issue. the symptoms and metadata issue was documented, but not the underlying cause of why the metadata was incorrect.

I'm mainly curious if downstreams from FreeBSD who provide their own package repos (like #HardenedBSD) might be impacted.