Report created on Thu Jun 29 10:56:58 2017. back to main menu


Enter a new maintainer (partial match is OK) to get information about their FreeBSD ports:

Maintainer: 

For explanatory information and summary details, see the notes below.

portname maintainer build error logs Problem Reports Responsible
archivers/libcabinet tj@FreeBSD.org      
archivers/mscompress tj@FreeBSD.org      
benchmarks/filebench tj@FreeBSD.org      
converters/dosunix tj@FreeBSD.org      
databases/p5-DBIx-Class-Helpers tj@FreeBSD.org      
databases/p5-DBIx-Introspector tj@FreeBSD.org      
databases/puppetdb-terminus4 tj@FreeBSD.org      
databases/puppetdb4 tj@FreeBSD.org      
databases/py-rb tj@FreeBSD.org      
devel/cflow tj@FreeBSD.org      
devel/cutils tj@FreeBSD.org      
devel/libcli tj@FreeBSD.org      
devel/p5-Config-Validator tj@FreeBSD.org      
devel/p5-Data-Rand tj@FreeBSD.org      
devel/p5-Data-Rand-Obscure tj@FreeBSD.org      
devel/p5-File-FcntlLock tj@FreeBSD.org      
devel/p5-File-LibMagic tj@FreeBSD.org      
devel/p5-JSON-Hyper tj@FreeBSD.org      
devel/p5-JSON-Schema tj@FreeBSD.org      
devel/p5-Log-Any-Adapter-Callback tj@FreeBSD.org      
devel/p5-Log-Dispatch-File-Rolling tj@FreeBSD.org      
devel/p5-MooseX-ArrayRef tj@FreeBSD.org      
devel/p5-MooseX-Types-PortNumber tj@FreeBSD.org      
devel/p5-Proc-BackOff tj@FreeBSD.org      
devel/p5-Term-Clui tj@FreeBSD.org      
devel/p5-autovivification tj@FreeBSD.org      
devel/p5-constant tj@FreeBSD.org      
devel/pear-PHPTAL tj@FreeBSD.org      
devel/pecl-ncurses tj@FreeBSD.org      
devel/py-exam tj@FreeBSD.org      
devel/py-petname tj@FreeBSD.org      
devel/py-pytest-django tj@FreeBSD.org      
devel/py-statsd tj@FreeBSD.org      
devel/py-twine tj@FreeBSD.org      
devel/py-voluptuous tj@FreeBSD.org      
devel/py3-voluptuous tj@FreeBSD.org      
devel/sigar tj@FreeBSD.org      
java/sigar tj@FreeBSD.org ???    
lang/p5-Promises tj@FreeBSD.org      
mail/py-email-reply-parser tj@FreeBSD.org      
net-mgmt/nagios-check_zpools tj@FreeBSD.org      
net-mgmt/p5-Net-NSCA-Client tj@FreeBSD.org      
net-mgmt/p5-jmx4perl tj@FreeBSD.org      
net/activemq tj@FreeBSD.org      
net/p5-Net-STOMP-Client tj@FreeBSD.org      
security/clamtk tj@FreeBSD.org      
security/lasso tj@FreeBSD.org      
security/py-python-social-auth tj@FreeBSD.org      
security/razorback-api tj@FreeBSD.org      
security/rubygem-razorback-scriptNugget tj@FreeBSD.org      
sysutils/logstash5 tj@FreeBSD.org      
sysutils/p5-File-Log tj@FreeBSD.org      
textproc/elasticsearch tj@FreeBSD.org      
textproc/elasticsearch2 tj@FreeBSD.org      
textproc/elasticsearch5 tj@FreeBSD.org      
textproc/elasticsearch5-x-pack tj@FreeBSD.org      
textproc/kibana5 tj@FreeBSD.org      
textproc/kibana5-x-pack tj@FreeBSD.org      
textproc/p5-RDF-Trine tj@FreeBSD.org      
textproc/p5-Search-Elasticsearch tj@FreeBSD.org      
textproc/p5-Search-Elasticsearch-Client-0_90 tj@FreeBSD.org      
textproc/p5-Search-Elasticsearch-Client-1_0 tj@FreeBSD.org      
textproc/p5-Search-Elasticsearch-Client-2_0 tj@FreeBSD.org      
textproc/p5-Text-CSV-Hashify tj@FreeBSD.org      
textproc/p5-XML-CommonNS tj@FreeBSD.org      
textproc/p5-XML-Entities tj@FreeBSD.org      
textproc/p5-XML-Namespace tj@FreeBSD.org      
textproc/p5-XML-NamespaceFactory tj@FreeBSD.org      
textproc/py-toronado tj@FreeBSD.org      
www/p5-Any-URI-Escape tj@FreeBSD.org      
www/p5-CGI-ExtDirect tj@FreeBSD.org      
www/p5-Dancer-Logger-Log4perl tj@FreeBSD.org      
www/p5-Dancer-Plugin-ExtDirect tj@FreeBSD.org      
www/p5-Dancer-Plugin-FlashMessage tj@FreeBSD.org      
www/p5-HTTP-Link-Parser tj@FreeBSD.org      
www/p5-Hijk tj@FreeBSD.org      
www/p5-LWP-Authen-Negotiate tj@FreeBSD.org      
www/p5-RPC-ExtDirect tj@FreeBSD.org      
www/py-django-configurations tj@FreeBSD.org      
www/py-django-jsonfield tj@FreeBSD.org      
www/py-django-paging tj@FreeBSD.org      
www/py-django-recaptcha tj@FreeBSD.org      
www/py-django-social-auth tj@FreeBSD.org      
www/py-django-sudo tj@FreeBSD.org      
www/py-django-templatetag-sugar tj@FreeBSD.org      
www/rubygem-dashing tj@FreeBSD.org      
ports shown: 86   ports with build errors: 1 ports with outstanding PRs: 0  
ports with either build errors or PRs: 1

Notes:

Clicking on each column heading will cause the report to be redone sorted by that column. Clicking again will reverse the sort.

The portname column includes links to a more complete overview for that port.

The maintainer column includes links to a page showing the status of all ports for that maintainer.

The build error logs column represents the list of unique errors noticed in any build environment (if any). The errors are listed alphabetically. Each entry is a link to a particular errorlog. (In cases where the same error occurs in multiple build environments, the latest errorlog is used.)

The list of build errors that are detected, and a short description of each one, can be found here.

The PRs (if any) for the given port are listed numerically in the Problem Reports column. Thus, for each port, they should also be in order from earliest to latest.

Currently, no effort is made to correlate any individual build error with any individual PR. They are listed in adjacent columns only for your viewing convenience.

The underlying technology of this report relies on trying to extract information from the existing PR database entries. These entries are entered by human users using the send-pr command. As such, the quality of the entries varies greatly.

The fastest, and easiest, information is gleaned from a PR entry whose subject line contains the port category and port name, separated by a slash. However, if this algorithm only flagged those, it would miss nearly 50% of the ports PRs, not to mention all the 'framework' PRs.

So, as an extension, various heuristics are used to guess what it is the user really intended. See the code in prQueryUtils.py for the gory details. What's important to understand is this: there is no possible algorithm that will correctly identify all the ambiguous PRs without getting a few false identifications and still run in less than geological time. So, before you are tempted to file a PR on this algorithm itself, read the code to understand its design tradeoffs, and then consider instead filing followup PRs to the ambiguous PRs that would disambiguate them instead. Thanks -- the author.