Report created on Wed Apr 26 08:03:22 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/pear-DoctrineCommon wg@FreeBSD.org      
databases/pear-DoctrineDBAL wg@FreeBSD.org      
databases/pear-DoctrineORM wg@FreeBSD.org      
databases/py-south wg@FreeBSD.org      
databases/py-sqlobject wg@FreeBSD.org      
databases/py-unqlite wg@FreeBSD.org      
databases/pymongo wg@FreeBSD.org      
databases/riak2 wg@FreeBSD.org      
devel/apiextractor wg@FreeBSD.org      
devel/ds2 wg@FreeBSD.org      
devel/libgit2 wg@FreeBSD.org linker_error    
devel/pear-Symfony_Component_Console wg@FreeBSD.org      
devel/pear-channel-doctrine wg@FreeBSD.org      
devel/py-babelfish wg@FreeBSD.org      
devel/py-billiard wg@FreeBSD.org      
devel/py-biplist wg@FreeBSD.org      
devel/py-celery wg@FreeBSD.org      
devel/py-cffi wg@FreeBSD.org      
devel/py-defusedxml wg@FreeBSD.org      
devel/py-docker-py wg@FreeBSD.org      
devel/py-dogpile.cache wg@FreeBSD.org      
devel/py-fastentrypoints wg@FreeBSD.org      
devel/py-flake8 wg@FreeBSD.org      
devel/py-freenas.dispatcher wg@FreeBSD.org      
devel/py-freenas.utils wg@FreeBSD.org      
devel/py-functools32 wg@FreeBSD.org      
devel/py-hghooks wg@FreeBSD.org      
devel/py-hgsubversion wg@FreeBSD.org      
devel/py-hgtools wg@FreeBSD.org      
devel/py-jaraco.timing wg@FreeBSD.org      
devel/py-jaraco.util wg@FreeBSD.org      
devel/py-jsonschema wg@FreeBSD.org      
devel/py-libzfs [I] wg@FreeBSD.org compiler_error    
devel/py-lockfile wg@FreeBSD.org      
devel/py-lxml wg@FreeBSD.org      
devel/py-mccabe wg@FreeBSD.org      
devel/py-mimeparse wg@FreeBSD.org      
devel/py-mongoengine wg@FreeBSD.org      
devel/py-more-itertools wg@FreeBSD.org      
devel/py-path.py wg@FreeBSD.org      
devel/py-paver wg@FreeBSD.org      
devel/py-polib wg@FreeBSD.org      
devel/py-ptvsd wg@FreeBSD.org      
devel/py-pycparser wg@FreeBSD.org      
devel/py-pygit2 wg@FreeBSD.org      
devel/py-pympler wg@FreeBSD.org      
devel/py-pyte wg@FreeBSD.org      
devel/py-pytest-runner wg@FreeBSD.org      
devel/py-rednose wg@FreeBSD.org      
devel/py-rose wg@FreeBSD.org      
devel/py-setuptools_scm wg@FreeBSD.org      
devel/py-sqlcc wg@FreeBSD.org      
devel/py-stsci.distutils wg@FreeBSD.org      
devel/py-sysctl wg@FreeBSD.org      
devel/py-termstyle wg@FreeBSD.org      
devel/py-tvrage wg@FreeBSD.org      
devel/py-unipath wg@FreeBSD.org      
devel/py-vcversioner wg@FreeBSD.org      
devel/py3-defusedxml wg@FreeBSD.org      
devel/py3-flake8 wg@FreeBSD.org      
devel/py3-hgtools wg@FreeBSD.org      
devel/py3-libzfs [I] wg@FreeBSD.org compiler_error    
devel/py3-lxml wg@FreeBSD.org      
devel/py3-mccabe wg@FreeBSD.org      
devel/py3-pytest-runner wg@FreeBSD.org      
devel/shiboken wg@FreeBSD.org coredump    
dns/inadyn-mt wg@FreeBSD.org      
ftp/yafc wg@FreeBSD.org      
irc/py-irc wg@FreeBSD.org      
lang/erlang-riak wg@FreeBSD.org runaway_process    
math/py-bitmath wg@FreeBSD.org      
misc/py-pexpect wg@FreeBSD.org      
misc/py-progressbar231 wg@FreeBSD.org      
multimedia/ffmpeg0 wg@FreeBSD.org      
multimedia/ffmpeg2theora wg@FreeBSD.org      
multimedia/gmerlin-avdecoder wg@FreeBSD.org      
multimedia/py-enzyme wg@FreeBSD.org      
multimedia/py-guessit wg@FreeBSD.org      
multimedia/py-librtmp wg@FreeBSD.org      
multimedia/py-subliminal wg@FreeBSD.org      
net/minidlna wg@FreeBSD.org      
net/py-amqp wg@FreeBSD.org      
net/py-kombu wg@FreeBSD.org      
net/py-netif wg@FreeBSD.org      
net/rclone wg@FreeBSD.org      
sysutils/ataidle wg@FreeBSD.org      
sysutils/gdisk wg@FreeBSD.org      
sysutils/hptcli wg@FreeBSD.org      
sysutils/patchelf wg@FreeBSD.org      
sysutils/py-cdmi wg@FreeBSD.org      
sysutils/py-freenas.cli wg@FreeBSD.org      
sysutils/restic wg@FreeBSD.org ???    
sysutils/riak-cs wg@FreeBSD.org      
sysutils/sample [I] wg@FreeBSD.org compiler_error    
sysutils/stanchion wg@FreeBSD.org      
textproc/libguess wg@FreeBSD.org      
textproc/py-pysrt wg@FreeBSD.org      
textproc/py-sphinxcontrib-httpdomain wg@FreeBSD.org      
textproc/py-ucl wg@FreeBSD.org      
www/dojo wg@FreeBSD.org      
www/py-beautifulsoup wg@FreeBSD.org      
www/py-django-assets wg@FreeBSD.org      
www/py-django-taggit wg@FreeBSD.org      
www/py-django-tastypie wg@FreeBSD.org      
www/py-formencode wg@FreeBSD.org      
www/py-requests-toolbelt wg@FreeBSD.org      
www/py-rhodecode wg@FreeBSD.org      
www/py-rollbar wg@FreeBSD.org      
www/py-splinter wg@FreeBSD.org      
www/py-tmdb3 wg@FreeBSD.org      
www/py-webassets wg@FreeBSD.org      
www/zend-framework wg@FreeBSD.org      
www/zend-framework1 wg@FreeBSD.org      
x11-wm/awesome-vicious wg@FreeBSD.org      
x11-wm/qtile wg@FreeBSD.org      
ports shown: 115   ports with build errors: 7 ports with outstanding PRs: 0  
ports with either build errors or PRs: 7

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.