Report created on Wed Jun 28 09:07:58 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/herrie ed@FreeBSD.org      
audio/ladspa arved@FreeBSD.org      
audio/xmms-ladspa arved@FreeBSD.org      
audio/xmms-mailnotify arved@FreeBSD.org      
benchmarks/netio arved@FreeBSD.org      
databases/jlog alfred@FreeBSD.org      
devel/argdata ed@FreeBSD.org      
devel/aws-sdk-cpp arved@FreeBSD.org runaway_process    
devel/cloudabi ed@FreeBSD.org      
devel/cloudabi-binutils-aarch64 ed@FreeBSD.org      
devel/cloudabi-binutils-x86_64 ed@FreeBSD.org      
devel/cloudabi-toolchain ed@FreeBSD.org      
devel/cobf ed@FreeBSD.org      
devel/colormake arved@FreeBSD.org      
devel/elfrc ed@FreeBSD.org      
devel/mimir ed@FreeBSD.org      
devel/py-fake-factory alfred@FreeBSD.org      
devel/py-kitchen arved@FreeBSD.org      
devel/py-monotonic alfred@FreeBSD.org      
devel/py-tipper alfred@FreeBSD.org      
devel/remake arved@FreeBSD.org      
devel/stfl arved@FreeBSD.org      
devel/websocketpp arved@FreeBSD.org      
dns/totd ed@FreeBSD.org      
games/lolcat arved@FreeBSD.org      
games/moon-buggy arved@FreeBSD.org      
lang/elan ed@FreeBSD.org      
misc/img2xterm arved@FreeBSD.org      
multimedia/libxspf ed@FreeBSD.org      
net-im/libmesode arved@FreeBSD.org      
net-im/libstrophe arved@FreeBSD.org      
net-im/poezio arved@FreeBSD.org      
net-im/profanity arved@FreeBSD.org      
net-im/py-sleekxmpp arved@FreeBSD.org      
net-mgmt/py-yapsnmp arved@FreeBSD.org      
net/libsocket++ arved@FreeBSD.org      
net/ssldump arved@FreeBSD.org      
net/uriparser ed@FreeBSD.org      
science/bddsolve ed@FreeBSD.org      
security/pcsc-tools arved@FreeBSD.org      
security/ssh_askpass_gtk2 arved@FreeBSD.org      
security/steghide arved@FreeBSD.org      
sysutils/cloudabi-utils ed@FreeBSD.org      
sysutils/hidesvn ed@FreeBSD.org      
textproc/luceneplusplus arved@FreeBSD.org      
www/newsbeuter arved@FreeBSD.org      
www/py-django-bootstrap-form alfred@FreeBSD.org      
www/py-django-countries alfred@FreeBSD.org      
www/py-django-formtools alfred@FreeBSD.org      
www/py-djangorestframework alfred@FreeBSD.org      
www/py-djangorestframework-csv alfred@FreeBSD.org      
www/py-djangorestframework-filters alfred@FreeBSD.org      
www/py-djangorestframework-xml alfred@FreeBSD.org      
www/py-websocket-client alfred@FreeBSD.org      
ports shown: 54   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.