Report created on Thu Mar 30 22:28:40 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
devel/libewf nobutaka@FreeBSD.org      
devel/libvshadow nobutaka@FreeBSD.org      
devel/p5-Data-Hexify nobutaka@FreeBSD.org      
devel/p5-Mac-PropertyList nobutaka@FreeBSD.org      
devel/p5-Parse-Win32Registry nobutaka@FreeBSD.org      
editors/apel nobutaka@FreeBSD.org      
editors/flim nobutaka@FreeBSD.org      
editors/semi nobutaka@FreeBSD.org      
japanese/anthy nobutaka@FreeBSD.org      
japanese/cmigemo nobutaka@FreeBSD.org      
japanese/cmigemo-dict nobutaka@FreeBSD.org      
japanese/eterm nobutaka@FreeBSD.org      
japanese/font-mona nobutaka@FreeBSD.org      
japanese/font-mona-ttf nobutaka@FreeBSD.org      
japanese/jmode nobutaka@FreeBSD.org      
japanese/jmode-skk nobutaka@FreeBSD.org      
japanese/kasumi nobutaka@FreeBSD.org      
japanese/migemo nobutaka@FreeBSD.org      
japanese/migemo-emacs23 nobutaka@FreeBSD.org      
japanese/migemo.el nobutaka@FreeBSD.org      
japanese/uim-anthy nobutaka@FreeBSD.org      
japanese/w3m nobutaka@FreeBSD.org      
japanese/w3m-img nobutaka@FreeBSD.org      
mail/wanderlust nobutaka@FreeBSD.org      
mail/wanderlust-devel nobutaka@FreeBSD.org      
net/dshell nobutaka@FreeBSD.org      
net/py-pygeoip nobutaka@FreeBSD.org      
net/tcpick nobutaka@FreeBSD.org      
net/tcpxtract nobutaka@FreeBSD.org      
security/log2timeline nobutaka@FreeBSD.org      
security/md5deep nobutaka@FreeBSD.org      
security/ssdeep nobutaka@FreeBSD.org      
sysutils/bulk_extractor nobutaka@FreeBSD.org      
sysutils/dc3dd nobutaka@FreeBSD.org ???    
sysutils/dcfldd nobutaka@FreeBSD.org      
sysutils/dd_rescue nobutaka@FreeBSD.org      
sysutils/ufs_copy nobutaka@FreeBSD.org      
textproc/uim nobutaka@FreeBSD.org      
textproc/uim-el nobutaka@FreeBSD.org      
textproc/uim-gtk nobutaka@FreeBSD.org      
textproc/uim-gtk3 nobutaka@FreeBSD.org      
textproc/uim-kde4 nobutaka@FreeBSD.org      
textproc/uim-m17nlib nobutaka@FreeBSD.org      
textproc/uim-qt4 nobutaka@FreeBSD.org      
www/emacs-w3m nobutaka@FreeBSD.org      
www/w3m nobutaka@FreeBSD.org      
www/w3m-img nobutaka@FreeBSD.org      
x11/mlterm nobutaka@FreeBSD.org      
ports shown: 48   ports with build errors: 1 ports with outstanding PRs: 0  
ports with either build errors or PRs: 1

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.