Report created on Thu Feb 23 16:40:53 2017. back to main menu

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

portname maintainer build error logs Problem Reports Responsible
archivers/libunrar4 ports@FreeBSD.org      
archivers/macutils ports@FreeBSD.org      
audio/libofa jhale@FreeBSD.org      
cad/brlcad erik@brlcad.org      
converters/p5-JSON-Any perl@FreeBSD.org      
databases/db48 ports@FreeBSD.org      
databases/jdbc-oracle10g [I] ports@FreeBSD.org      
databases/jdbc-oracle8i [I] ports@FreeBSD.org      
databases/jdbc-oracle9i [I] ports@FreeBSD.org      
databases/oracle7-client ports@FreeBSD.org      
databases/oracle8-client ports@FreeBSD.org      
databases/p5-DBD-Oracle perl@FreeBSD.org      
databases/puppetdb freebsd@zleslie.info      
databases/puppetdb-terminus freebsd@geoffgarside.co.uk      
databases/py-sqlalchemy09 m.tsatsenko@gmail.com      
databases/yasql ports@FreeBSD.org      
devel/liborcus07 office@FreeBSD.org      
devel/mdds0 office@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-Test-Block lth@FreeBSD.org      
devel/py-Jinja nivit@FreeBSD.org      
devel/py-TGScheduler wen@FreeBSD.org      
devel/py-TurboJinja nivit@FreeBSD.org      
devel/py-ll-core ports@FreeBSD.org      
devel/py-mez_xml ports@FreeBSD.org      
devel/py-tgMochiKit wen@FreeBSD.org      
devel/py-turbocheetah nivit@FreeBSD.org      
devel/py-turbojson nivit@FreeBSD.org      
devel/py-turbojson11 nivit@FreeBSD.org      
devel/py-turbokid nivit@FreeBSD.org      
devel/rubygem-bson1 ruby@FreeBSD.org      
devel/rubygem-builder32 ruby@FreeBSD.org      
devel/rubygem-minitest4 ruby@FreeBSD.org      
dns/opendnssec13 jaap@NLnetLabs.nl      
editors/libreoffice4 office@FreeBSD.org      
emulators/hyperv-is [I] bsdic@microsoft.com      
graphics/rayshade ports@FreeBSD.org      
graphics/urt [B] ports@FreeBSD.org      
japanese/ruby-eb ruby@FreeBSD.org      
japanese/xyaku ports@FreeBSD.org      
java/jdk16-doc [I] java@FreeBSD.org      
java/jdk7-doc [I] java@FreeBSD.org      
lang/perl5.20 perl@FreeBSD.org      
lang/perl5.22 perl@FreeBSD.org      
lang/python33 python@FreeBSD.org      
mail/p5-Net-SMTP-SSL sunpoet@FreeBSD.org      
mail/py-turbomail python@FreeBSD.org      
misc/p5-Geo-Coder-Geocoder-US sunpoet@FreeBSD.org      
misc/p5-Geo-Coder-Many sunpoet@FreeBSD.org      
net/tcpdump398 [F] ports@FreeBSD.org      
ports-mgmt/fbsdmon [I] ports@FreeBSD.org      
security/krb5-113 cy@FreeBSD.org      
security/openvpn23 mandree@FreeBSD.org      
security/openvpn23-polarssl mandree@FreeBSD.org      
security/pgp ports@FreeBSD.org      
sysutils/iocage robak@FreeBSD.org      
sysutils/iocage-devel kmoore@FreeBSD.org      
sysutils/jail2 yamagi@yamagi.org      
sysutils/linux-nero emulation@FreeBSD.org      
sysutils/osquery [B] zi@FreeBSD.org      
sysutils/puppet38 ruby@FreeBSD.org      
sysutils/xacpim henriknj@0xmilk.org      
textproc/rubygem-github-markdown ruby@FreeBSD.org      
textproc/rubygem-liquid2 ruby@FreeBSD.org      
textproc/rubygem-nokogiri14 ruby@FreeBSD.org      
textproc/rubygem-sass-rails4 ruby@FreeBSD.org      
www/apache22 apache@FreeBSD.org      
www/cocoon ports@FreeBSD.org      
www/moodle29 wen@FreeBSD.org      
www/node012 bradleythughes@fastmail.fm      
www/npm012 jpaetzel@FreeBSD.org      
www/py-GinGin ports@FreeBSD.org      
www/py-Lightbox nivit@FreeBSD.org      
www/py-django-pipeline13 ports@FreeBSD.org      
www/py-django16 python@FreeBSD.org      
www/py-scriptaculous python@FreeBSD.org      
www/py-tgwebservices python@FreeBSD.org      
www/py-turbogears python@FreeBSD.org      
www/rubygem-mechanize26 ruby@FreeBSD.org      
www/rubygem-net-http-digest_auth11 ruby@FreeBSD.org      
www/rubygem-rack14 ruby@FreeBSD.org      
x11/lumina-i18n [B] kmoore@FreeBSD.org      
ports shown: 85   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.