Report created on Sun Mar 26 15:15:23 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/arj garga@FreeBSD.org coredump    
archivers/sharutils garga@FreeBSD.org      
audio/beep garga@FreeBSD.org      
converters/tnef garga@FreeBSD.org      
devel/git garga@FreeBSD.org      
devel/git-gui garga@FreeBSD.org      
devel/git-lite garga@FreeBSD.org      
devel/git-subversion garga@FreeBSD.org      
devel/libslang2 garga@FreeBSD.org      
devel/pecl-newt garga@FreeBSD.org      
devel/sysconftool garga@FreeBSD.org      
editors/jed garga@FreeBSD.org      
ftp/ftpmirror garga@FreeBSD.org      
irc/bitlbee garga@FreeBSD.org      
mail/mb2md garga@FreeBSD.org      
mail/pear-Mail garga@FreeBSD.org      
mail/razor-agents garga@FreeBSD.org      
mail/wmbiff garga@FreeBSD.org      
math/slgrace garga@FreeBSD.org      
misc/compat7x garga@FreeBSD.org      
net-im/pidgin-hotkeys garga@FreeBSD.org      
net-im/twirssi garga@FreeBSD.org      
net-mgmt/choparp garga@FreeBSD.org      
net/dpinger garga@FreeBSD.org      
net/libpcap garga@FreeBSD.org      
net/mobile-broadband-provider-info garga@FreeBSD.org      
net/pear-Net_Growl garga@FreeBSD.org      
net/pear-Net_IPv6 garga@FreeBSD.org      
net/pecl-zmq garga@FreeBSD.org      
net/rinetd garga@FreeBSD.org      
net/tcpdump garga@FreeBSD.org      
net/wmnd garga@FreeBSD.org      
net/xmlrpc-c garga@FreeBSD.org ???    
security/checkpassword garga@FreeBSD.org      
security/clamav garga@FreeBSD.org      
security/clamav-milter garga@FreeBSD.org      
security/keychain garga@FreeBSD.org      
security/scanhill garga@FreeBSD.org      
security/sudo garga@FreeBSD.org      
security/xinetd garga@FreeBSD.org      
shells/psh garga@FreeBSD.org      
shells/scponly garga@FreeBSD.org      
sysutils/wmcube garga@FreeBSD.org      
sysutils/wmcube-gdk garga@FreeBSD.org      
textproc/po4a garga@FreeBSD.org      
www/dotproject garga@FreeBSD.org      
www/sarg garga@FreeBSD.org      
www/squidguard garga@FreeBSD.org      
x11-fonts/artwiz-aleczapka garga@FreeBSD.org      
x11-fonts/artwiz-fonts garga@FreeBSD.org      
x11-wm/awesome garga@FreeBSD.org      
x11/gmrun garga@FreeBSD.org      
x11/xcb-util garga@FreeBSD.org      
x11/xcb-util-image garga@FreeBSD.org      
x11/xcb-util-keysyms garga@FreeBSD.org      
x11/xcb-util-renderutil garga@FreeBSD.org      
x11/xcb-util-wm garga@FreeBSD.org      
ports shown: 57   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.