Report created on Mon May 22 17:33:27 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      
converters/p5-JSON-Any perl@FreeBSD.org      
databases/db48 ports@FreeBSD.org      
databases/pgpool-II kuriyama@FreeBSD.org      
databases/pgpool-II-30 kuriyama@FreeBSD.org      
devel/arduino-glcd [B] leres@ee.lbl.gov      
devel/cld [B] demon@FreeBSD.org      
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-Penguin perl@FreeBSD.org      
devel/p5-Test-Block perl@FreeBSD.org      
dns/opendnssec13 jaap@NLnetLabs.nl      
dns/pear-Net_DNS joneum@FreeBSD.org      
games/libgames-support gnome@FreeBSD.org      
graphics/py-graph-dot [B] demon@FreeBSD.org      
lang/perl5.20 perl@FreeBSD.org      
lang/perl5.22 perl@FreeBSD.org      
lang/python33 python@FreeBSD.org      
mail/dovecot ports@FreeBSD.org      
mail/dovecot-antispam dsh@wizard.volgograd.ru      
mail/dovecot-managesieve dgeo@centrale-marseille.fr      
mail/dovecot-sieve yds@CoolRat.org      
mail/dovecot2-antispam-plugin olgeni@FreeBSD.org      
mail/linux-thunderbird gecko@FreeBSD.org      
mail/p5-Net-SMTP-SSL sunpoet@FreeBSD.org      
mail/pgpsendmail ports@FreeBSD.org      
math/bargraph [B] dereckson@gmail.com      
misc/p5-Geo-Coder-Many sunpoet@FreeBSD.org      
multimedia/avbin [B] amdmi3@FreeBSD.org      
multimedia/banshee [B] mono@FreeBSD.org      
multimedia/py-ffmpeg dbn@FreeBSD.org      
net/sixxs-aiccu ports@FreeBSD.org      
ports-mgmt/fbsdmon [I] ports@FreeBSD.org      
security/krb5-113 cy@FreeBSD.org      
security/p5-Crypt-PGPSimple bofh@FreeBSD.org      
security/pgp ports@FreeBSD.org      
security/radamsa [B] jau@iki.fi      
sysutils/ansible1 lifanov@FreeBSD.org      
sysutils/flyback [B] ports@FreeBSD.org      
www/apache22 apache@FreeBSD.org      
www/mediawiki126 wen@FreeBSD.org      
x11-toolkits/qt5-declarative kde@FreeBSD.org      
x11-wm/awesome3 garga@FreeBSD.org      
ports shown: 45   ports with build errors: 0 ports with outstanding PRs: 0  
ports with either build errors or PRs: 0

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.