The FreeBSD Ports Monitoring System

Here is a set of reports that allow anyone to query the state of the FreeBSD ports system by browsing through the data space of (portname X architecture X OS release X build error X Problem Reports). See below for more detailed explanation; or, if you just want to browse, start with the status of one port or the status of all ports for one maintainer.

Here's a more detailed guide to the available reports.

Basic reports:

type of report what is shown comments
build errors all ports by portname  
error counts by build environment  
error counts by category  
error percents by build environment  
error type by build environment  
build errors and Problem Reports all ports by portname  
all ports for one maintainer, by portname  
error counts by maintainer  
all ports with PRs assigned to one Responsible, by portname  
all ports with PRs assigned to no-one, by portname  
ports marked BROKEN, by portname ports that will not build or run, for one reason or another
ports marked DEPRECATED, by portname ports which users are discouraged from installing, for one reason or another
ports marked with an EXPIRATION_DATE, by portname ports scheduled to be removed in the near future, for one reason or another
ports marked FORBIDDEN, by portname ports with security problems
ports marked IGNORE, by portname ports which might not install, for one reason or another
ports marked NO_STAGE, by portname ports which need to catch up with infrastructure changes to avoid being deprecated
ports with errors in one build environment, by portname  
overall status summary number of ports PRs, number of ports that don't build by build environment, and so forth
Problem Reports existing ports by portname  
existing ports by PR number  
framework by PR number  
new ports by PR number  
repocopies requested by PR number  
unknown by PR number whatever the PR classification algorithm can't fit into "existing ports", "framework", "new ports", or "repocopies"
status of one port summary select any port you want

Specialized reports:

type of report what is shown comments
anomalies summary possible problems within the ports tree and the GNATS database
dependency trees dependency tree for one port (since it runs 'make depend', it's really slow.)
Problem Reports all, by PR number (a sanity check for the PR classification algorithm)
ports which have moved, by portname  
ports with maintainer updates, by portname  
ports where maintainer is a committer, by portname helps to identify PRs needing assignment (but watch for false positives)
ports where maintainer is not a committer, by portname  
ports where maintainer might not know, by portname e.g. maintainer is neither a committer nor the PR submittter; helps to identify PRs needing reminders (but watch for false positives)
ports with no maintainer, by portname  
ports with possibly misconveyed PRs, by portname (not yet useable due to a high number of false identifications of ports)
PRs which are in the 'feedback' state, by PR number helps to identify PRs with possible submitter or maintainer timeouts

Notes

The data that these reports are built out is from several sources, as follows:

I'd be interested in getting feedback from anyone about their thoughts or questions about this technology via "linimon at lonesome.com".

Last updated Tue Jun 3 05:06:58 UTC 2014