Report created on Mon Aug 21 13:46:34 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
archivers/py-lzma sbz@FreeBSD.org      
comms/py-serial sbz@FreeBSD.org      
devel/9base sbz@FreeBSD.org      
devel/colorgcc sbz@FreeBSD.org      
devel/dissy sbz@FreeBSD.org      
devel/elfkickers sbz@FreeBSD.org      
devel/libixp sbz@FreeBSD.org      
devel/pep8 sbz@FreeBSD.org      
devel/py-InlineEgg [B] sbz@FreeBSD.org      
devel/py-aspects sbz@FreeBSD.org      
devel/py-aspyct sbz@FreeBSD.org      
devel/py-bitarray sbz@FreeBSD.org      
devel/py-bitstring sbz@FreeBSD.org      
devel/py-deliciousapi sbz@FreeBSD.org      
devel/py-iterpipes sbz@FreeBSD.org      
devel/py-meliae sbz@FreeBSD.org      
devel/py-phabricator sbz@FreeBSD.org      
devel/py-ptrace sbz@FreeBSD.org      
devel/py-setproctitle sbz@FreeBSD.org      
devel/py-usb sbz@FreeBSD.org      
devel/py3-setproctitle sbz@FreeBSD.org      
devel/runsnakerun sbz@FreeBSD.org      
devel/strace sbz@FreeBSD.org      
dns/dns2tcp sbz@FreeBSD.org      
editors/gobby sbz@FreeBSD.org      
graphics/py-gvgen sbz@FreeBSD.org      
irc/ii sbz@FreeBSD.org      
net/googlecl sbz@FreeBSD.org      
net/hexinject sbz@FreeBSD.org      
net/panoptis sbz@FreeBSD.org      
net/py-dpkt sbz@FreeBSD.org      
net/py-libnet sbz@FreeBSD.org      
net/scnc sbz@FreeBSD.org      
net/tcpslice sbz@FreeBSD.org      
security/dsniff sbz@FreeBSD.org      
security/honggfuzz sbz@FreeBSD.org new_compiler_error    
security/knock sbz@FreeBSD.org      
security/knocker sbz@FreeBSD.org      
security/libssh2 sbz@FreeBSD.org      
security/p5-Net-SinFP sbz@FreeBSD.org      
security/py-PF sbz@FreeBSD.org      
security/py-openssl sbz@FreeBSD.org      
security/py-paramiko sbz@FreeBSD.org      
security/py3-openssl sbz@FreeBSD.org      
security/sinfp sbz@FreeBSD.org      
sysutils/goaccess sbz@FreeBSD.org      
sysutils/ldapvi sbz@FreeBSD.org      
sysutils/ltrace sbz@FreeBSD.org      
sysutils/pax-utils sbz@FreeBSD.org      
textproc/jid sbz@FreeBSD.org      
textproc/py-feedparser sbz@FreeBSD.org      
www/roundup sbz@FreeBSD.org      
x11-toolkits/py-SquareMap sbz@FreeBSD.org      
x11/arandr sbz@FreeBSD.org      
ports shown: 54   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.