Report created on Mon Sep 25 13:38:25 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/deco kevlo@FreeBSD.org      
astro/gmapcatcher [B] kevlo@FreeBSD.org      
astro/py-horoscopegenerator kevlo@FreeBSD.org      
astro/py-pywapi kevlo@FreeBSD.org      
audio/py-speechrecognition kevlo@FreeBSD.org      
comms/librs232 kevlo@FreeBSD.org      
converters/py-zfec kevlo@FreeBSD.org      
deskutils/taskcoach kevlo@FreeBSD.org      
devel/deheader kevlo@FreeBSD.org      
devel/iniparser kevlo@FreeBSD.org      
devel/libdisorder kevlo@FreeBSD.org      
devel/p5-Regexp-Subst-Parallel kevlo@FreeBSD.org      
devel/p5-String-Similarity kevlo@FreeBSD.org      
devel/p5-Tie-RegexpHash kevlo@FreeBSD.org      
devel/py-foolscap kevlo@FreeBSD.org      
devel/umlgraph kevlo@FreeBSD.org      
ftp/atftp kevlo@FreeBSD.org      
games/gbrainy kevlo@FreeBSD.org      
graphics/py-imageio kevlo@FreeBSD.org      
graphics/py-imgurpython kevlo@FreeBSD.org      
mail/poppy kevlo@FreeBSD.org      
math/algotutor kevlo@FreeBSD.org      
math/p5-Math-RPN kevlo@FreeBSD.org      
multimedia/audiopreview kevlo@FreeBSD.org      
multimedia/py-cec kevlo@FreeBSD.org      
multimedia/py-moviepy kevlo@FreeBSD.org      
multimedia/recordmydesktop kevlo@FreeBSD.org      
net-im/p5-Net-ICQ2000 kevlo@FreeBSD.org      
net-im/pebrot kevlo@FreeBSD.org      
net-im/py-telepot kevlo@FreeBSD.org      
net-im/telegram-purple kevlo@FreeBSD.org      
net/ntlmaps kevlo@FreeBSD.org      
net/pecl-smbclient kevlo@FreeBSD.org      
net/py-nnpy kevlo@FreeBSD.org      
sysutils/ipad_charge kevlo@FreeBSD.org      
sysutils/synergy kevlo@FreeBSD.org      
sysutils/zbackup kevlo@FreeBSD.org      
textproc/p5-Text-Match-FastAlternatives kevlo@FreeBSD.org      
textproc/source-highlight kevlo@FreeBSD.org      
textproc/tinyxml kevlo@FreeBSD.org      
textproc/tkdiff kevlo@FreeBSD.org      
textproc/zenxml kevlo@FreeBSD.org      
www/cppcms kevlo@FreeBSD.org      
www/hotcrp kevlo@FreeBSD.org      
www/htmlcxx kevlo@FreeBSD.org      
www/jinzora kevlo@FreeBSD.org      
www/kplaylist kevlo@FreeBSD.org      
www/libjwt kevlo@FreeBSD.org      
www/phpmp kevlo@FreeBSD.org      
www/py-Tenjin kevlo@FreeBSD.org      
x11-fonts/comic-neue kevlo@FreeBSD.org      
x11-fonts/noto kevlo@FreeBSD.org      
x11-fonts/noto-lite kevlo@FreeBSD.org      
x11-fonts/ubuntu-font kevlo@FreeBSD.org      
ports shown: 54   ports with build errors: 0 ports with outstanding PRs: 0  
ports with either build errors or PRs: 0

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.