Report created on Sat Sep 23 09:03:32 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/radix.v2 cs@FreeBSD.org      
databases/redigo cs@FreeBSD.org      
devel/go-bayesian cs@FreeBSD.org      
devel/go-cobra cs@FreeBSD.org      
devel/go-codec cs@FreeBSD.org      
devel/go-faker cs@FreeBSD.org      
devel/go-form cs@FreeBSD.org      
devel/go-glide cs@FreeBSD.org      
devel/go-go.uuid cs@FreeBSD.org      
devel/go-gocode cs@FreeBSD.org      
devel/go-goregen cs@FreeBSD.org      
devel/go-logrus cs@FreeBSD.org      
devel/go-metrics cs@FreeBSD.org      
devel/go-pflag cs@FreeBSD.org      
devel/go-protobuf cs@FreeBSD.org      
devel/go-tools cs@FreeBSD.org      
devel/go-yaml cs@FreeBSD.org      
devel/goprotobuf cs@FreeBSD.org      
devel/pijul cs@FreeBSD.org      
devel/py-extras cs@FreeBSD.org      
devel/py-subvertpy cs@FreeBSD.org      
devel/py-transaction cs@FreeBSD.org      
devel/pyobfuscate cs@FreeBSD.org      
games/gnubg cs@FreeBSD.org linker_error    
games/nettoe cs@FreeBSD.org      
graphics/pixelize cs@FreeBSD.org      
net-im/xmpp-client cs@FreeBSD.org      
net/go-bapu cs@FreeBSD.org      
net/go-httppath cs@FreeBSD.org      
net/go-httptreemux cs@FreeBSD.org      
net/onioncat cs@FreeBSD.org      
science/py-DendroPy cs@FreeBSD.org      
security/arm cs@FreeBSD.org      
security/goptlib cs@FreeBSD.org      
security/libotr cs@FreeBSD.org      
security/libotr3 cs@FreeBSD.org      
security/meek cs@FreeBSD.org      
security/obfsproxy cs@FreeBSD.org      
security/py-YubiOTP cs@FreeBSD.org      
security/py-gnupg cs@FreeBSD.org      
security/py-pyptlib cs@FreeBSD.org      
security/py-stem cs@FreeBSD.org      
security/switzerland cs@FreeBSD.org      
sysutils/wemux cs@FreeBSD.org      
textproc/scss cs@FreeBSD.org      
www/imgsizer cs@FreeBSD.org      
www/py-WebTest cs@FreeBSD.org      
www/py-django-annoying cs@FreeBSD.org      
www/py-django-classy-tags cs@FreeBSD.org      
www/py-django-evolution cs@FreeBSD.org      
www/py-django-markdownx cs@FreeBSD.org      
www/py-django-mptt cs@FreeBSD.org      
www/py-django-otp cs@FreeBSD.org      
www/py-django-otp-yubikey cs@FreeBSD.org      
www/py-django-simple-history cs@FreeBSD.org      
www/py-surl cs@FreeBSD.org      
ports shown: 56   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.