Report created on Thu Jul 27 16:51:14 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/flowgrind dbaio@FreeBSD.org      
devel/pear-Validate dbaio@FreeBSD.org      
devel/pecl-svn dbaio@FreeBSD.org      
devel/py-cluster dbaio@FreeBSD.org      
devel/py-darts.util.lru dbaio@FreeBSD.org      
devel/py-http-prompt dbaio@FreeBSD.org      
devel/py-mailcap-fix dbaio@FreeBSD.org      
devel/py-phply dbaio@FreeBSD.org      
devel/py-ply dbaio@FreeBSD.org      
devel/py-stopit dbaio@FreeBSD.org      
devel/py-tblib dbaio@FreeBSD.org      
devel/py3-ply dbaio@FreeBSD.org      
games/robocode dbaio@FreeBSD.org      
games/robocode-naval dbaio@FreeBSD.org      
irc/znc dbaio@FreeBSD.org      
mail/isoqlog dbaio@FreeBSD.org      
mail/pear-Mail_mimeDecode dbaio@FreeBSD.org      
mail/pecl-mailparse [I] dbaio@FreeBSD.org      
mail/pecl-mailparse2 dbaio@FreeBSD.org      
math/pecl-stats dbaio@FreeBSD.org      
math/pecl-stats2 [I] dbaio@FreeBSD.org      
misc/ansiweather dbaio@FreeBSD.org      
misc/solarized dbaio@FreeBSD.org      
net-im/pecl-stomp dbaio@FreeBSD.org      
net-im/pecl-stomp2 [I] dbaio@FreeBSD.org      
net-mgmt/ipv6calc dbaio@FreeBSD.org manpage    
net/pecl-oauth dbaio@FreeBSD.org      
net/pecl-oauth2 [I] dbaio@FreeBSD.org      
net/py-httpstat dbaio@FreeBSD.org      
net/py-python-ntlm dbaio@FreeBSD.org      
science/silo dbaio@FreeBSD.org      
security/chaosreader dbaio@FreeBSD.org      
security/libscrypt dbaio@FreeBSD.org      
security/medusa dbaio@FreeBSD.org      
security/pecl-scrypt dbaio@FreeBSD.org      
security/pecl-ssh2 [I] dbaio@FreeBSD.org      
security/pecl-ssh2-0 dbaio@FreeBSD.org      
security/py-halberd dbaio@FreeBSD.org      
security/py-vulndb dbaio@FreeBSD.org      
security/w3af dbaio@FreeBSD.org      
sysutils/apcupsd dbaio@FreeBSD.org      
sysutils/downtimed dbaio@FreeBSD.org      
sysutils/duplicity dbaio@FreeBSD.org      
sysutils/f3 dbaio@FreeBSD.org      
sysutils/prips dbaio@FreeBSD.org      
sysutils/pslist dbaio@FreeBSD.org      
sysutils/py-scriptine dbaio@FreeBSD.org      
sysutils/smenu dbaio@FreeBSD.org      
textproc/extract_url dbaio@FreeBSD.org      
textproc/pear-File_MARC dbaio@FreeBSD.org      
textproc/pear-Validate_ISPN dbaio@FreeBSD.org      
textproc/pecl-xdiff dbaio@FreeBSD.org      
textproc/pecl-xdiff2 [I] dbaio@FreeBSD.org      
textproc/pecl-yaml [I] dbaio@FreeBSD.org      
textproc/pecl-yaml1 dbaio@FreeBSD.org      
textproc/py-esmre dbaio@FreeBSD.org      
textproc/py-guess-language dbaio@FreeBSD.org      
textproc/py-html2text dbaio@FreeBSD.org      
textproc/py-parsimonious dbaio@FreeBSD.org      
textproc/py-pystemmer dbaio@FreeBSD.org      
textproc/py-texttable dbaio@FreeBSD.org      
textproc/py3-pystemmer dbaio@FreeBSD.org      
textproc/py3-texttable dbaio@FreeBSD.org      
www/axis2 dbaio@FreeBSD.org      
www/kannel dbaio@FreeBSD.org      
www/kannel-sqlbox dbaio@FreeBSD.org      
www/libwww dbaio@FreeBSD.org      
www/rtv dbaio@FreeBSD.org      
x11/py-xdot dbaio@FreeBSD.org      
ports shown: 69   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.