Report created on Sat Mar 25 07:46:22 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/p5-Compress-Bzip2 demon@FreeBSD.org      
audio/p5-MP3-Info demon@FreeBSD.org      
converters/p5-Convert-Recode demon@FreeBSD.org      
converters/p5-Convert-UU demon@FreeBSD.org      
converters/recode demon@FreeBSD.org      
databases/hbase demon@FreeBSD.org      
databases/nagios-check_mongodb demon@FreeBSD.org      
databases/nagios-check_redis demon@FreeBSD.org      
databases/py-motor demon@FreeBSD.org      
devel/cgilib demon@FreeBSD.org      
devel/cld [B] demon@FreeBSD.org      
devel/cld2 demon@FreeBSD.org      
devel/gaa demon@FreeBSD.org      
devel/hadoop demon@FreeBSD.org      
devel/hadoop2 demon@FreeBSD.org      
devel/hive demon@FreeBSD.org      
devel/libmatheval demon@FreeBSD.org arch    
devel/oozie demon@FreeBSD.org      
devel/p5-App-Info demon@FreeBSD.org      
devel/p5-ExtUtils-ParseXS demon@FreeBSD.org      
devel/p5-Locale-gettext demon@FreeBSD.org      
devel/p5-Module-Info demon@FreeBSD.org      
devel/p5-Proc-Simple demon@FreeBSD.org      
devel/p5-Resources demon@FreeBSD.org      
devel/p5-Term-ReadKey demon@FreeBSD.org      
devel/p5-Test-More-UTF8 demon@FreeBSD.org      
devel/p5-TimeDate demon@FreeBSD.org      
devel/p5-Tree-Simple demon@FreeBSD.org      
devel/p5-capitalization demon@FreeBSD.org      
devel/pig [B] demon@FreeBSD.org      
devel/protobuf25 demon@FreeBSD.org      
devel/py-cld demon@FreeBSD.org      
devel/py-country demon@FreeBSD.org      
devel/py-phonenumbers demon@FreeBSD.org      
devel/py-pydoop demon@FreeBSD.org      
devel/py-ua_parser demon@FreeBSD.org      
devel/py-user_agents demon@FreeBSD.org      
devel/spark demon@FreeBSD.org ???    
devel/ua_parser-core demon@FreeBSD.org      
devel/uatraits demon@FreeBSD.org      
dns/py-pycares demon@FreeBSD.org      
ftp/uftp demon@FreeBSD.org      
graphics/gource demon@FreeBSD.org      
graphics/py-graph demon@FreeBSD.org      
graphics/py-graph-core demon@FreeBSD.org      
graphics/py-graph-dot [B] demon@FreeBSD.org      
mail/mini_sendmail demon@FreeBSD.org      
mail/p5-Mail-MboxParser demon@FreeBSD.org      
mail/p5-Mail-POP3Client demon@FreeBSD.org      
math/foma [B] demon@FreeBSD.org      
math/hfst demon@FreeBSD.org      
math/mosesdecoder demon@FreeBSD.org      
math/openfst demon@FreeBSD.org      
math/py-theano demon@FreeBSD.org      
math/sfst demon@FreeBSD.org      
math/vowpal_wabbit demon@FreeBSD.org      
misc/bbjd demon@FreeBSD.org      
misc/p5-I18N-Charset demon@FreeBSD.org      
misc/p5-I18N-LangTags demon@FreeBSD.org      
misc/p5-Locale-Codes demon@FreeBSD.org      
misc/vera demon@FreeBSD.org      
net-mgmt/nagios-check_netsnmp demon@FreeBSD.org      
net-mgmt/p5-SNMP_Session demon@FreeBSD.org      
net/clusterit demon@FreeBSD.org      
net/haproxy demon@FreeBSD.org linker_error    
net/haproxy-devel [I] demon@FreeBSD.org      
net/p5-Net-RawIP demon@FreeBSD.org      
net/p5-Net-Whois demon@FreeBSD.org      
net/p5-Net-Z3950-SimpleServer demon@FreeBSD.org      
net/p5-Net-Z3950-ZOOM demon@FreeBSD.org      
net/py-haproxy-log-analysis demon@FreeBSD.org      
net/traceroute demon@FreeBSD.org      
net/xferstats demon@FreeBSD.org      
net/yaz++ demon@FreeBSD.org      
net/yazproxy demon@FreeBSD.org      
science/py-scikit-learn demon@FreeBSD.org      
sysutils/ascpu demon@FreeBSD.org      
sysutils/oak demon@FreeBSD.org      
sysutils/p5-SyslogScan demon@FreeBSD.org      
sysutils/puppet-mode.el demon@FreeBSD.org      
sysutils/ts demon@FreeBSD.org      
textproc/irstlm demon@FreeBSD.org      
textproc/kenlm demon@FreeBSD.org      
textproc/man2html demon@FreeBSD.org      
textproc/opengrm-ngram demon@FreeBSD.org new_compiler_error    
textproc/p5-MARC demon@FreeBSD.org      
textproc/p5-MARC-Lint demon@FreeBSD.org      
textproc/p5-MARC-Record demon@FreeBSD.org      
textproc/p5-MARC-XML demon@FreeBSD.org      
textproc/p5-XML-Validate demon@FreeBSD.org      
textproc/py-nltk demon@FreeBSD.org      
textproc/py-pygtail demon@FreeBSD.org      
textproc/py-tinycss demon@FreeBSD.org      
textproc/randlm demon@FreeBSD.org ???    
www/calamaris demon@FreeBSD.org      
www/calamaris-devel demon@FreeBSD.org      
www/mod_proxy_uwsgi demon@FreeBSD.org      
www/p5-HTML-Summary demon@FreeBSD.org      
www/p5-HTML-TableLayout demon@FreeBSD.org      
www/p5-HTTP-Server-Simple-Mason demon@FreeBSD.org      
www/py-django-htmlmin demon@FreeBSD.org      
www/uwsgitop demon@FreeBSD.org      
www/webcrawl demon@FreeBSD.org      
ports shown: 103   ports with build errors: 5 ports with outstanding PRs: 0  
ports with either build errors or PRs: 5

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.