Report created on Wed May 24 21:37:50 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/9e rodrigo@FreeBSD.org      
archivers/rpm4 rodrigo@FreeBSD.org      
archivers/unace rodrigo@FreeBSD.org      
audio/lmms rodrigo@FreeBSD.org      
comms/gammu rodrigo@FreeBSD.org      
devel/jrtplib rodrigo@FreeBSD.org ???    
devel/libarena rodrigo@FreeBSD.org      
devel/libassa rodrigo@FreeBSD.org      
devel/libast rodrigo@FreeBSD.org      
devel/libatomic_ops rodrigo@FreeBSD.org      
devel/libaura rodrigo@FreeBSD.org      
devel/libavl rodrigo@FreeBSD.org      
devel/libcfg rodrigo@FreeBSD.org      
devel/libcii rodrigo@FreeBSD.org      
devel/libdfui rodrigo@FreeBSD.org      
devel/libelf rodrigo@FreeBSD.org      
devel/libgetline rodrigo@FreeBSD.org      
devel/libhash rodrigo@FreeBSD.org      
devel/libmsocket rodrigo@FreeBSD.org      
devel/libmtrie rodrigo@FreeBSD.org      
devel/libnaji rodrigo@FreeBSD.org      
devel/liboop rodrigo@FreeBSD.org      
devel/libredblack rodrigo@FreeBSD.org      
devel/libtai rodrigo@FreeBSD.org      
devel/libtap rodrigo@FreeBSD.org      
devel/libtermkey rodrigo@FreeBSD.org      
devel/libxalloc rodrigo@FreeBSD.org      
devel/log4c rodrigo@FreeBSD.org      
devel/mm rodrigo@FreeBSD.org      
devel/npm-amdefine rodrigo@FreeBSD.org runaway_process    
devel/npm-clean-css rodrigo@FreeBSD.org      
devel/npm-commander rodrigo@FreeBSD.org      
devel/npm-graceful-readlink rodrigo@FreeBSD.org runaway_process    
devel/npm-source-map rodrigo@FreeBSD.org      
devel/trio rodrigo@FreeBSD.org ???    
dns/dualserver rodrigo@FreeBSD.org      
editors/omegaT rodrigo@FreeBSD.org      
editors/poedit rodrigo@FreeBSD.org      
ftp/ftpsync rodrigO@FreeBSD.org      
graphics/ufraw rodrigo@FreeBSD.org      
irc/cgiirc rodrigo@FreeBSD.org      
multimedia/podcastdl rodrigo@FreeBSD.org ???    
net-mgmt/cowpatty rodrigo@FreeBSD.org      
net-mgmt/rrdbot rodrigo@FreeBSD.org      
net-mgmt/smokeping rodrigo@FreeBSD.org      
net/splatd rodrigo@FreeBSD.org      
net/wakeonlan rodrigo@FreeBSD.org      
russian/ircd-hybrid rodrigo@FreeBSD.org clang    
shells/pdksh rodrigo@FreeBSD.org      
sysutils/fusefs-curlftpfs rodrigo@FreeBSD.org      
sysutils/fusefs-gstfs rodrigo@FreeBSD.org      
sysutils/logtool rodrigo@FreeBSD.org      
textproc/p5-libsoldout rodrigo@FreeBSD.org      
textproc/rss2html rodrigo@FreeBSD.org      
textproc/smu rodrigo@FreeBSD.org      
www/c-icap-modules rodrigo@FreeBSD.org      
www/dfileserver rodrigo@FreeBSD.org      
www/lessc rodrigo@FreeBSD.org runaway_process    
www/mod_memcache rodrigo@FreeBSD.org      
www/multisort rodrigo@FreeBSD.org      
www/npm-less-plugin-clean-css rodrigo@FreeBSD.org      
www/p5-HTML-Template-Associate rodrigo@FreeBSD.org      
www/p5-WWW-FreeProxy rodrigo@FreeBSD.org      
www/yabb rodrigo@FreeBSD.org      
x11-clocks/buici-clock rodrigo@FreeBSD.org      
x11-fm/librfm rodrigo@FreeBSD.org      
x11-fm/libtubo rodrigo@FreeBSD.org      
x11-fm/rodent rodrigo@FreeBSD.org      
x11/tilda rodrigo@FreeBSD.org      
ports shown: 69   ports with build errors: 7 ports with outstanding PRs: 0  
ports with either build errors or PRs: 7

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.