Report created on Sun Jun 25 12:21:03 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
audio/abraca madpilot@FreeBSD.org      
audio/asterisk-espeak madpilot@FreeBSD.org      
audio/asterisk-flite madpilot@FreeBSD.org      
audio/bcg729 madpilot@FreeBSD.org      
audio/cpp-xmms2 madpilot@FreeBSD.org      
audio/gxmms2 madpilot@FreeBSD.org      
audio/p5-xmms2 madpilot@FreeBSD.org      
audio/py-xmms2 madpilot@FreeBSD.org      
audio/xmms2 madpilot@FreeBSD.org      
comms/gnokii madpilot@FreeBSD.org      
comms/obexapp madpilot@FreeBSD.org      
comms/openobex madpilot@FreeBSD.org      
comms/smstools3 madpilot@FreeBSD.org      
databases/sqliteodbc madpilot@FreeBSD.org      
databases/sqliteodbc-sqlite2 madpilot@FreeBSD.org clang    
deskutils/calibre madpilot@FreeBSD.org      
devel/courier-unicode madpilot@FreeBSD.org      
devel/geany madpilot@FreeBSD.org      
devel/geany-plugin-addons madpilot@FreeBSD.org      
devel/geany-plugin-autoclose madpilot@FreeBSD.org      
devel/geany-plugin-automark madpilot@FreeBSD.org      
devel/geany-plugin-codenav madpilot@FreeBSD.org      
devel/geany-plugin-commander madpilot@FreeBSD.org      
devel/geany-plugin-ctags madpilot@FreeBSD.org      
devel/geany-plugin-debugger madpilot@FreeBSD.org      
devel/geany-plugin-defineformat madpilot@FreeBSD.org      
devel/geany-plugin-devhelp madpilot@FreeBSD.org      
devel/geany-plugin-doc madpilot@FreeBSD.org      
devel/geany-plugin-extrasel madpilot@FreeBSD.org      
devel/geany-plugin-geanypy madpilot@FreeBSD.org      
devel/geany-plugin-gendoc madpilot@FreeBSD.org      
devel/geany-plugin-geniuspaste madpilot@FreeBSD.org      
devel/geany-plugin-git-changebar madpilot@FreeBSD.org      
devel/geany-plugin-insertnum madpilot@FreeBSD.org      
devel/geany-plugin-latex madpilot@FreeBSD.org      
devel/geany-plugin-lineoperations madpilot@FreeBSD.org      
devel/geany-plugin-lipsum madpilot@FreeBSD.org      
devel/geany-plugin-lua madpilot@FreeBSD.org      
devel/geany-plugin-macro madpilot@FreeBSD.org      
devel/geany-plugin-markdown madpilot@FreeBSD.org      
devel/geany-plugin-miniscript madpilot@FreeBSD.org      
devel/geany-plugin-multiterm madpilot@FreeBSD.org      
devel/geany-plugin-numberedbookmarks madpilot@FreeBSD.org      
devel/geany-plugin-overview madpilot@FreeBSD.org      
devel/geany-plugin-pairtaghighlighter madpilot@FreeBSD.org      
devel/geany-plugin-pg madpilot@FreeBSD.org      
devel/geany-plugin-pohelper madpilot@FreeBSD.org      
devel/geany-plugin-pretty-printer madpilot@FreeBSD.org      
devel/geany-plugin-prj madpilot@FreeBSD.org      
devel/geany-plugin-projectorganizer madpilot@FreeBSD.org      
devel/geany-plugin-scope madpilot@FreeBSD.org      
devel/geany-plugin-sendmail madpilot@FreeBSD.org      
devel/geany-plugin-shiftcolumn madpilot@FreeBSD.org      
devel/geany-plugin-spellcheck madpilot@FreeBSD.org      
devel/geany-plugin-tableconvert madpilot@FreeBSD.org      
devel/geany-plugin-treebrowser madpilot@FreeBSD.org      
devel/geany-plugin-updatechecker madpilot@FreeBSD.org      
devel/geany-plugin-vc madpilot@FreeBSD.org      
devel/geany-plugin-webhelper madpilot@FreeBSD.org      
devel/geany-plugin-xmlsnippets madpilot@FreeBSD.org      
devel/geany-plugins madpilot@FreeBSD.org      
devel/geany-plugins-l10n madpilot@FreeBSD.org      
devel/jsmin madpilot@FreeBSD.org      
devel/yaml-cpp madpilot@FreeBSD.org      
finance/gnucash madpilot@FreeBSD.org      
finance/gnucash-docs madpilot@FreeBSD.org      
games/0ad madpilot@FreeBSD.org      
games/corsix-th madpilot@FreeBSD.org      
games/freesynd madpilot@FreeBSD.org      
games/netpanzer madpilot@FreeBSD.org      
games/pokerth madpilot@FreeBSD.org      
games/traindirector madpilot@FreeBSD.org      
graphics/amide madpilot@FreeBSD.org      
graphics/volpack madpilot@FreeBSD.org      
mail/maildrop madpilot@FreeBSD.org      
multimedia/libva madpilot@FreeBSD.org      
multimedia/libva-intel-driver madpilot@FreeBSD.org      
multimedia/libva-utils madpilot@FreeBSD.org      
multimedia/libva-vdpau-driver madpilot@FreeBSD.org      
multimedia/libvdpau madpilot@FreeBSD.org      
multimedia/libvdpau-va-gl madpilot@FreeBSD.org      
multimedia/vdpauinfo madpilot@FreeBSD.org      
net/asterisk-g72x madpilot@FreeBSD.org      
net/asterisk11 madpilot@FreeBSD.org configure_error    
net/asterisk13 madpilot@FreeBSD.org configure_error    
net/ndpi madpilot@FreeBSD.org      
net/ntopng madpilot@FreeBSD.org      
net/pjsip madpilot@FreeBSD.org      
net/pjsip-extsrtp madpilot@FreeBSD.org      
net/unison madpilot@FreeBSD.org      
net/unison-devel [I] madpilot@FreeBSD.org      
net/unison240 madpilot@FreeBSD.org      
sysutils/conky madpilot@FreeBSD.org      
sysutils/conky-awesome madpilot@FreeBSD.org      
www/chpasswd madpilot@FreeBSD.org      
www/phprecipebook madpilot@FreeBSD.org      
x11-toolkits/girara madpilot@FreeBSD.org      
x11/trayer madpilot@FreeBSD.org      
ports shown: 98   ports with build errors: 3 ports with outstanding PRs: 0  
ports with either build errors or PRs: 3

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.