Report created on Thu Jun 29 10:59:47 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/nuttcp pi@FreeBSD.org      
biology/seqtools pi@FreeBSD.org      
converters/p5-Convert-Base32 pi@FreeBSD.org      
converters/p5-Encoding-BER pi@FreeBSD.org      
databases/cego pi@FreeBSD.org      
databases/cegobridge pi@FreeBSD.org ???    
databases/linux-oracle-instantclient-basic [I] pi@FreeBSD.org      
databases/linux-oracle-instantclient-sdk [I] pi@FreeBSD.org      
databases/linux-oracle-instantclient-sqlplus [I] pi@FreeBSD.org      
databases/mysqltuner pi@FreeBSD.org      
databases/p5-DBD-cego pi@FreeBSD.org      
databases/p5-File-Locate pi@FreeBSD.org      
databases/pecl-mongodb pi@FreeBSD.org      
databases/sqlrelay pi@FreeBSD.org      
devel/antlr4 pi@FreeBSD.org      
devel/dragon pi@FreeBSD.org      
devel/lfcbase pi@FreeBSD.org manpage    
devel/lfcxml pi@FreeBSD.org      
devel/p5-CBOR-XS pi@FreeBSD.org      
devel/p5-Object-Import pi@FreeBSD.org      
devel/p5-PerlIO-via-Timeout pi@FreeBSD.org      
devel/p5-String-Dump pi@FreeBSD.org      
devel/p5-Test-RequiresInternet pi@FreeBSD.org      
devel/pcc-libs pi@FreeBSD.org      
devel/py-raven pi@FreeBSD.org      
devel/py-stdnum pi@FreeBSD.org      
devel/rudiments pi@FreeBSD.org      
devel/soapui pi@FreeBSD.org      
devel/vtable-dumper pi@FreeBSD.org      
dns/adns pi@FreeBSD.org      
dns/dnsviz pi@FreeBSD.org      
dns/p5-Net-RNDC pi@FreeBSD.org      
dns/p5-URBL-Prepare pi@FreeBSD.org      
emulators/py-gns3-converter pi@FreeBSD.org      
graphics/p5-feedgnuplot pi@FreeBSD.org      
mail/imapsync pi@FreeBSD.org      
mail/libsrs2 pi@FreeBSD.org      
mail/libsrs_alt pi@FreeBSD.org      
mail/msglint pi@FreeBSD.org      
math/p5-Math-Int128 pi@FreeBSD.org      
net-im/oysttyer pi@FreeBSD.org      
net-mgmt/arpwatch pi@FreeBSD.org      
net-mgmt/bgpuma pi@FreeBSD.org      
net-mgmt/kismet pi@FreeBSD.org      
net-mgmt/ndpmon pi@FreeBSD.org      
net-mgmt/nfdump pi@FreeBSD.org      
net-mgmt/p0f pi@FreeBSD.org      
net-mgmt/pmacct pi@FreeBSD.org      
net/kamailio pi@FreeBSD.org      
net/owamp pi@FreeBSD.org      
net/p5-IO-Socket-Timeout pi@FreeBSD.org      
net/p5-Net-Works pi@FreeBSD.org      
net/quagga pi@FreeBSD.org      
net/rdapper pi@FreeBSD.org      
net/sip_scenario pi@FreeBSD.org      
print/fig2dev pi@FreeBSD.org      
print/transfig pi@FreeBSD.org      
security/binwalk pi@FreeBSD.org      
security/p5-Auth-YubikeyDecrypter pi@FreeBSD.org      
security/p5-Crypt-Format pi@FreeBSD.org      
security/p5-Crypt-OpenSSL-PKCS10 pi@FreeBSD.org      
security/p5-Crypt-RSA-Parse pi@FreeBSD.org      
security/p5-Digest-GOST pi@FreeBSD.org ???    
security/p5-Protocol-ACME pi@FreeBSD.org      
security/p5-SAVI-Perl [I] pi@FreeBSD.org      
security/revealrk pi@FreeBSD.org      
security/tls-check pi@FreeBSD.org      
textproc/htmltolatex pi@FreeBSD.org      
www/cmsmadesimple pi@FreeBSD.org      
www/litmus pi@FreeBSD.org      
www/p5-HTML-Perlinfo pi@FreeBSD.org      
www/p5-Selenium-Remote-Driver pi@FreeBSD.org      
www/p5-Test-LWP-UserAgent pi@FreeBSD.org      
www/p5-WWW-Mechanize-PhantomJS pi@FreeBSD.org      
www/p5-libapreq2 pi@FreeBSD.org      
x11-toolkits/p5-Tk pi@FreeBSD.org      
x11-toolkits/p5-Tk-FontDialog pi@FreeBSD.org      
x11/p5-X11-XCB pi@FreeBSD.org      
x11/p5-X11-Xlib pi@FreeBSD.org      
ports shown: 79   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.