Report created on Fri Apr 28 10:16:00 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
benchmarks/dbench jlaffaye@FreeBSD.org      
benchmarks/httperf jlaffaye@FreeBSD.org      
databases/cdb jlaffaye@FreeBSD.org      
databases/soci jlaffaye@FreeBSD.org ???    
devel/py-python-gflags jlaffaye@FreeBSD.org      
devel/re2 jlaffaye@FreeBSD.org      
dns/dlint jlaffaye@FreeBSD.org      
irc/libircclient jlaffaye@FreeBSD.org      
lang/go jlaffaye@FreeBSD.org      
lang/go14 jlaffaye@FreeBSD.org ???    
multimedia/cclive jlaffaye@FreeBSD.org      
net-mgmt/whatmask jlaffaye@FreeBSD.org      
net/go.net jlaffaye@FreeBSD.org      
news/py-yenc jlaffaye@FreeBSD.org      
print/libharu jlaffaye@FreeBSD.org ???    
print/py-pdf jlaffaye@FreeBSD.org      
security/go.crypto jlaffaye@FreeBSD.org      
textproc/discount jlaffaye@FreeBSD.org      
textproc/go.text jlaffaye@FreeBSD.org      
www/closure-compiler jlaffaye@FreeBSD.org      
www/closure-linter [B] jlaffaye@FreeBSD.org      
www/py-feedgenerator jlaffaye@FreeBSD.org      
www/py-pelican jlaffaye@FreeBSD.org      
www/py-scgi jlaffaye@FreeBSD.org      
www/wadcomblog jlaffaye@FreeBSD.org      
x11/bgs jlaffaye@FreeBSD.org      
x11/sselp jlaffaye@FreeBSD.org      
ports shown: 27   ports with build errors: 3 ports with outstanding PRs: 0  
ports with either build errors or PRs: 3

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.