Report created on Mon May 1 02:48:29 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
databases/mysql56-client mmokhi@FreeBSD.org      
databases/mysql56-server mmokhi@FreeBSD.org ???    
databases/mysql57-client mmokhi@FreeBSD.org ???    
databases/mysql57-server mmokhi@FreeBSD.org ???    
databases/mysql80-client mmokhi@FreeBSD.org ???    
databases/mysql80-server mmokhi@FreeBSD.org ???    
devel/byaccj mmokhi@FreeBSD.org      
devel/csmith mmokhi@FreeBSD.org      
devel/elf mmokhi@FreeBSD.org      
devel/frama-c mmokhi@FreeBSD.org      
devel/libccid mmokhi@FreeBSD.org      
devel/libtuntap mmokhi@FreeBSD.org      
devel/pcsc-lite mmokhi@FreeBSD.org      
devel/py-enum-compat mmokhi@FreeBSD.org      
devel/py-gdbgui mmokhi@FreeBSD.org      
devel/py-pygdbmi mmokhi@FreeBSD.org      
devel/py-pypugjs mmokhi@FreeBSD.org      
devel/py-python-engineio mmokhi@FreeBSD.org      
devel/py-python-socketio mmokhi@FreeBSD.org      
editors/codelite mmokhi@FreeBSD.org      
games/glest mmokhi@FreeBSD.org      
games/lincity-ng mmokhi@FreeBSD.org      
games/mari0 mmokhi@FreeBSD.org      
games/xtux mmokhi@FreeBSD.org      
lang/cling mmokhi@FreeBSD.org linker_error    
multimedia/librespot mmokhi@FreeBSD.org ???    
net-mgmt/netdata mmokhi@FreeBSD.org compiler_error
gcc4_error
   
sysutils/liburcu mmokhi@FreeBSD.org      
sysutils/lttng-tools mmokhi@FreeBSD.org      
sysutils/lttng-ust mmokhi@FreeBSD.org      
www/py-flask-socketio mmokhi@FreeBSD.org      
x11/grabc mmokhi@FreeBSD.org      
ports shown: 32   ports with build errors: 8 ports with outstanding PRs: 0  
ports with either build errors or PRs: 8

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.