Report created on Sat Mar 25 03:49:05 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/makeself jadawin@FreeBSD.org      
archivers/p5-Archive-Tar jadawin@FreeBSD.org      
deskutils/remind jadawin@FreeBSD.org      
devel/p5-Config-General jadawin@FreeBSD.org      
devel/p5-DateTime-Format-W3CDTF jadawin@FreeBSD.org      
devel/p5-DateTime-TimeZone jadawin@FreeBSD.org      
devel/p5-Lexical-Persistence jadawin@FreeBSD.org      
devel/p5-SNMP-Persist jadawin@FreeBSD.org      
devel/perlconsole jadawin@FreeBSD.org      
editors/hexcurse jadawin@FreeBSD.org      
games/banihstypos jadawin@FreeBSD.org      
irc/irssi-scripts jadawin@FreeBSD.org      
irc/irssi-xmpp jadawin@FreeBSD.org clang    
mail/p5-Mail-IMAPClient jadawin@FreeBSD.org      
mail/vrfy jadawin@FreeBSD.org      
math/p5-Math-BaseCalc jadawin@FreeBSD.org      
misc/mirmon jadawin@FreeBSD.org      
misc/yaunc jadawin@FreeBSD.org      
net-mgmt/disco jadawin@FreeBSD.org      
net-mgmt/p5-Net-CIDR jadawin@FreeBSD.org      
net-mgmt/p5-SNMP-Info jadawin@FreeBSD.org      
net-p2p/rtgui [B] jadawin@FreeBSD.org      
net/p5-Net-Proxy jadawin@FreeBSD.org      
net/p5-Net-SSH2 jadawin@FreeBSD.org      
net/raggle jadawin@FreeBSD.org      
net/uplog jadawin@FreeBSD.org      
security/p5-IO-Socket-SSL jadawin@FreeBSD.org      
security/p5-Nmap-Parser jadawin@FreeBSD.org      
sysutils/hourglass jadawin@FreeBSD.org      
sysutils/p5-Unix-Processors jadawin@FreeBSD.org compiler_error    
sysutils/tenshi jadawin@FreeBSD.org      
textproc/p5-PDF-Create jadawin@FreeBSD.org      
textproc/txt2html jadawin@FreeBSD.org      
www/checkbot jadawin@FreeBSD.org      
www/p5-HTML-Parser jadawin@FreeBSD.org      
www/p5-W3C-LinkChecker jadawin@FreeBSD.org      
www/p5-WWW-Scraper-ISBN-ORA_Driver jadawin@FreeBSD.org      
www/surfraw jadawin@FreeBSD.org      
ports shown: 38   ports with build errors: 2 ports with outstanding PRs: 0  
ports with either build errors or PRs: 2

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.