Report created on Wed Sep 20 21:57:07 2017. back to main menu

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

portname maintainer build error logs Problem Reports Responsible
astro/gmapcatcher [B] kevlo@FreeBSD.org      
audio/shairport miks.mikelsons@gmail.com      
converters/p5-JSON-Any perl@FreeBSD.org      
databases/db48 ports@FreeBSD.org      
databases/puppetdb-terminus3 puppet@FreeBSD.org      
databases/puppetdb3 puppet@FreeBSD.org      
devel/arduino-glcd [B] leres@FreeBSD.org      
devel/cld [B] demon@FreeBSD.org      
devel/libclaw amdmi3@FreeBSD.org      
devel/p5-Log-Any-Adapter-Syslog bill.brinzer@gmail.com      
devel/p5-MooseX-AttributeHelpers perl@FreeBSD.org      
devel/p5-MooseX-Daemonize perl@FreeBSD.org      
devel/p5-MooseX-Declare perl@FreeBSD.org      
devel/p5-MooseX-Role-WithOverloading perl@FreeBSD.org      
devel/p5-Test-Block perl@FreeBSD.org      
devel/py-twisted152 python@FreeBSD.org      
devel/py-twistedCore python@FreeBSD.org      
devel/py-twistedFlow neal@nelson.name      
devel/py-twistedRunner python@FreeBSD.org      
devel/vtcl ports@FreeBSD.org      
dns/py-twistedNames python@FreeBSD.org      
dns/rubygem-public_suffix2 sunpoet@FreeBSD.org      
editors/tpad ports@FreeBSD.org      
editors/vanubi ports@FreeBSD.org      
games/opensurge nemysis@FreeBSD.org      
games/polypuzzle ports@FreeBSD.org      
graphics/py-graph-dot [B] demon@FreeBSD.org      
lang/fpc-tcl acm@FreeBSD.org      
lang/gcc46 gerald@FreeBSD.org      
lang/gcc5-aux ports@FreeBSD.org ???    
lang/perl5.22 perl@FreeBSD.org      
lang/tcl84 tcltk@FreeBSD.org      
mail/milter-greylist-devel freebsd-ports@dan.me.uk      
mail/p5-Net-SMTP-SSL sunpoet@FreeBSD.org      
mail/py-twistedMail python@FreeBSD.org      
math/bargraph [B] dereckson@gmail.com      
multimedia/nxtvepg ports@FreeBSD.org      
multimedia/plexhometheater [B] woodsb02@FreeBSD.org      
net-im/py-twistedWords python@FreeBSD.org      
net-mgmt/nagios-check_bacula5 dan@langille.org      
net/asterisk11 madpilot@FreeBSD.org      
net/py-python-cloudfiles ports@FreeBSD.org      
net/py-twistedPair python@FreeBSD.org      
net/xpvm ports@FreeBSD.org      
news/py-twistedNews python@FreeBSD.org      
ports-mgmt/kpackagekit kde@FreeBSD.org      
ports-mgmt/packagekit-qt4 [I] gnome@FreeBSD.org      
ports-mgmt/redports-node ports@FreeBSD.org      
security/gnupg20 adamw@FreeBSD.org      
security/krb5-113 cy@FreeBSD.org      
security/py-twistedConch python@FreeBSD.org      
security/radamsa [B] jau@iki.fi      
sysutils/ansible1 lifanov@FreeBSD.org      
sysutils/bacula5-bat dan@langille.org      
sysutils/bacula5-client dan@langille.org      
sysutils/bacula5-client-static dan@langille.org      
sysutils/bacula5-docs dan@langille.org      
sysutils/bacula5-server dan@langille.org      
sysutils/socket wosch@FreeBSD.org      
textproc/py-twistedLore python@FreeBSD.org      
www/apache22 apache@FreeBSD.org      
www/moodle30 wen@FreeBSD.org      
www/py-twistedWeb python@FreeBSD.org      
www/py-twistedWeb2 python@FreeBSD.org      
www/rubygem-deckar01-task_list1 sunpoet@FreeBSD.org      
www/rubygem-webpack-rails sunpoet@FreeBSD.org      
x11-fonts/alfont [B] nemysis@FreeBSD.org      
x11-toolkits/tk84 tcltk@FreeBSD.org      
x11-wm/awesome3 garga@FreeBSD.org      
x11/tkXwin dsh@vlink.ru      
ports shown: 70   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.