Report created on Wed Apr 26 07:54:58 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/par2cmdline martymac@FreeBSD.org      
archivers/par2cmdline-tbb martymac@FreeBSD.org      
audio/gnaural martymac@FreeBSD.org      
audio/gtick martymac@FreeBSD.org      
benchmarks/bonnie++ martymac@FreeBSD.org      
benchmarks/nttcp martymac@FreeBSD.org      
comms/gqrx martymac@FreeBSD.org      
comms/gr-osmosdr martymac@FreeBSD.org      
comms/rtl-sdr martymac@FreeBSD.org      
deskutils/notecase martymac@FreeBSD.org      
devel/raknet martymac@FreeBSD.org ???    
devel/simgear martymac@FreeBSD.org      
devel/tbb martymac@FreeBSD.org      
editors/yzis martymac@FreeBSD.org ???    
emulators/dolphin-emu martymac@FreeBSD.org      
emulators/jzintv martymac@FreeBSD.org      
emulators/pcsxr martymac@FreeBSD.org      
ftp/lftp martymac@FreeBSD.org      
games/afternoonstalker martymac@FreeBSD.org      
games/belooted martymac@FreeBSD.org      
games/blobby martymac@FreeBSD.org ???    
games/briquolo martymac@FreeBSD.org      
games/burgerspace martymac@FreeBSD.org      
games/cosmosmash martymac@FreeBSD.org      
games/flightgear martymac@FreeBSD.org      
games/flightgear-aircraft martymac@FreeBSD.org      
games/flightgear-data martymac@FreeBSD.org      
games/flightgear-mb339-pan martymac@FreeBSD.org      
games/jfsw martymac@FreeBSD.org      
games/openalchemist martymac@FreeBSD.org      
games/openjazz martymac@FreeBSD.org      
games/trackballs martymac@FreeBSD.org      
games/triplane martymac@FreeBSD.org      
graphics/pencil martymac@FreeBSD.org compiler_error    
graphics/tif22pnm martymac@FreeBSD.org      
multimedia/libdvdnav martymac@FreeBSD.org      
multimedia/libdvdread martymac@FreeBSD.org      
multimedia/sms1xxx-kmod [I] martymac@FreeBSD.org      
net/grsync martymac@FreeBSD.org      
net/ldapscripts martymac@FreeBSD.org      
security/fakeroot martymac@FreeBSD.org      
security/vlock martymac@FreeBSD.org      
sysutils/backupchecker martymac@FreeBSD.org      
sysutils/dvdvideo martymac@FreeBSD.org      
sysutils/evtviewer martymac@FreeBSD.org      
sysutils/fpart martymac@FreeBSD.org      
sysutils/pv martymac@FreeBSD.org      
ports shown: 47   ports with build errors: 4 ports with outstanding PRs: 0  
ports with either build errors or PRs: 4

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.