Report created on Fri Nov 28 00:17:35 2014. back to main menu

NOTE: as of 20140601, GNATS has been deprecated. Until portsmon can catch up, expect the PR data to be stale.

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
databases/py-htsql koobs@FreeBSD.org  
databases/py-htsql-mysql koobs@FreeBSD.org  
databases/py-htsql-pgsql koobs@FreeBSD.org  
databases/py-pylibmc koobs@FreeBSD.org  
databases/py-redis koobs@FreeBSD.org  
databases/py-riak koobs@FreeBSD.org  
databases/py-umemcache koobs@FreeBSD.org  
devel/buildbot koobs@FreeBSD.org  
devel/buildbot-slave koobs@FreeBSD.org  
devel/concurrencykit koobs@FreeBSD.org  
devel/euca2ools koobs@FreeBSD.org  
devel/libhtp koobs@FreeBSD.org  
devel/py-asyncio koobs@FreeBSD.org  
devel/py-blinker koobs@FreeBSD.org  
devel/py-capstone koobs@FreeBSD.org  
devel/py-circuits koobs@FreeBSD.org  
devel/py-d2to1 koobs@FreeBSD.org  
devel/py-dateutil koobs@FreeBSD.org  
devel/py-doit koobs@FreeBSD.org  
devel/py-fabric koobs@FreeBSD.org  
devel/py-futures koobs@FreeBSD.org  
devel/py-iso8601 koobs@FreeBSD.org  
devel/py-lazy koobs@FreeBSD.org  
devel/py-nose koobs@FreeBSD.org  
devel/py-omnijson koobs@FreeBSD.org  
devel/py-pbr koobs@FreeBSD.org  
devel/py-posix_ipc koobs@FreeBSD.org  
devel/py-pyflakes koobs@FreeBSD.org  
devel/py-pygithub koobs@FreeBSD.org  
devel/py-rauth koobs@FreeBSD.org  
devel/py-riak_pb koobs@FreeBSD.org  
devel/py-sanetime koobs@FreeBSD.org  
devel/py-tox koobs@FreeBSD.org  
devel/rebar koobs@FreeBSD.org  
devel/yasm-devel koobs@FreeBSD.org  
games/live-f1 koobs@FreeBSD.org  
graphics/py-pillow koobs@FreeBSD.org  
lang/spidermonkey185 koobs@FreeBSD.org  
mail/py-spambayes koobs@FreeBSD.org  
math/picosat koobs@FreeBSD.org  
math/py-graphillion koobs@FreeBSD.org  
math/py-pycosat koobs@FreeBSD.org  
multimedia/libx264 koobs@FreeBSD.org  
multimedia/x264 koobs@FreeBSD.org  
net-mgmt/bsnmp-regex koobs@FreeBSD.org  
net/czmq koobs@FreeBSD.org  
net/libzmq2 koobs@FreeBSD.org  
net/libzmq3 koobs@FreeBSD.org  
net/libzmq4 koobs@FreeBSD.org  
net/py-beanstalkc koobs@FreeBSD.org  
net/py-port-for koobs@FreeBSD.org  
net/py-pynsq koobs@FreeBSD.org  
net/py-pysendfile koobs@FreeBSD.org  
net/py-twitter-tools koobs@FreeBSD.org  
net/turses koobs@FreeBSD.org  
security/libprelude koobs@FreeBSD.org  
security/py-cpe koobs@FreeBSD.org  
security/py-cryptography koobs@FreeBSD.org  
security/py-oauthlib koobs@FreeBSD.org  
security/py-passlib koobs@FreeBSD.org  
security/py-pycrypto koobs@FreeBSD.org  
security/py-pysha3 koobs@FreeBSD.org  
security/py-rsa koobs@FreeBSD.org  
security/suricata koobs@FreeBSD.org  
sysutils/bsdploy koobs@FreeBSD.org  
sysutils/libfvde koobs@FreeBSD.org  
sysutils/py-execnet koobs@FreeBSD.org  
sysutils/py-ezjailremote koobs@FreeBSD.org  
sysutils/py-nagiosplugin koobs@FreeBSD.org  
sysutils/py-ploy koobs@FreeBSD.org  
sysutils/py-ploy_ansible koobs@FreeBSD.org  
sysutils/py-ploy_ec2 koobs@FreeBSD.org  
sysutils/py-ploy_ezjail koobs@FreeBSD.org  
sysutils/py-ploy_fabric koobs@FreeBSD.org  
textproc/py-markdown koobs@FreeBSD.org  
textproc/py-pytidylib koobs@FreeBSD.org  
textproc/py-transifex-client koobs@FreeBSD.org  
www/geeknote koobs@FreeBSD.org  
www/libhtp-suricata koobs@FreeBSD.org  
www/py-aiohttp koobs@FreeBSD.org  
www/py-bleach koobs@FreeBSD.org  
www/py-django-dpaste koobs@FreeBSD.org  
www/py-django-mezzanine koobs@FreeBSD.org  
www/py-django-mezzanine-filebrowser koobs@FreeBSD.org  
www/py-django-mezzanine-grappelli koobs@FreeBSD.org  
www/py-evernote koobs@FreeBSD.org  
www/py-grequests koobs@FreeBSD.org  
www/py-gunicorn koobs@FreeBSD.org  
www/py-praw koobs@FreeBSD.org  
www/py-rackspace-monitoring koobs@FreeBSD.org  
www/py-requestbuilder koobs@FreeBSD.org  
www/py-requests koobs@FreeBSD.org  
www/py-requests-oauthlib koobs@FreeBSD.org  
www/py-requests1 koobs@FreeBSD.org  
www/py-slumber koobs@FreeBSD.org  
ports shown: 95   ports with build errors: 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.