Report created on Wed Jun 28 05:20:34 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
chinese/cnprint lwhsu@FreeBSD.org      
databases/py-alembic lwhsu@FreeBSD.org      
databases/py-pgxnclient lwhsu@FreeBSD.org      
databases/py-pyhs lwhsu@FreeBSD.org      
databases/py-pymysql lwhsu@FreeBSD.org      
databases/py-pytc lwhsu@FreeBSD.org      
databases/py-sqlalchemy-migrate lwhsu@FreeBSD.org      
devel/hachoir-core lwhsu@FreeBSD.org      
devel/hachoir-parser lwhsu@FreeBSD.org      
devel/hachoir-regex lwhsu@FreeBSD.org      
devel/jenkins lwhsu@FreeBSD.org      
devel/p5-Data-RoundRobin lwhsu@FreeBSD.org      
devel/py-argparse lwhsu@FreeBSD.org      
devel/py-cjson lwhsu@FreeBSD.org      
devel/py-coverage lwhsu@FreeBSD.org      
devel/py-cxx lwhsu@FreeBSD.org      
devel/py-ezpyinline lwhsu@FreeBSD.org      
devel/py-jenkins-job-builder lwhsu@FreeBSD.org      
devel/py-magic lwhsu@FreeBSD.org      
devel/py-multi_key_dict lwhsu@FreeBSD.org      
devel/py-notifier lwhsu@FreeBSD.org      
devel/py-parsedatetime lwhsu@FreeBSD.org      
devel/py-pp lwhsu@FreeBSD.org      
devel/py-pycallgraph lwhsu@FreeBSD.org      
devel/py-python-jenkins lwhsu@FreeBSD.org      
devel/py-pytz lwhsu@FreeBSD.org      
devel/py-sysv_ipc lwhsu@FreeBSD.org      
devel/py-trace2html lwhsu@FreeBSD.org      
devel/py-urlimport lwhsu@FreeBSD.org      
devel/pycount lwhsu@FreeBSD.org      
devel/pythontidy lwhsu@FreeBSD.org      
devel/riscv64-binutils lwhsu@FreeBSD.org      
devel/riscv64-gcc lwhsu@FreeBSD.org      
devel/splint lwhsu@FreeBSD.org      
emulators/qemu-riscv [I] lwhsu@FreeBSD.org      
emulators/riscv-fesvr lwhsu@FreeBSD.org      
emulators/riscv-isa-sim lwhsu@FreeBSD.org      
ftp/py-ftputil lwhsu@FreeBSD.org      
ftp/py-pyftpdlib lwhsu@FreeBSD.org      
lang/cdent lwhsu@FreeBSD.org      
math/cvc3 lwhsu@FreeBSD.org      
math/py-bitvector lwhsu@FreeBSD.org      
math/py-igraph lwhsu@FreeBSD.org      
math/py-pybloom lwhsu@FreeBSD.org      
net/py-amqplib lwhsu@FreeBSD.org      
print/pdfcube lwhsu@FreeBSD.org      
security/py-gnutls lwhsu@FreeBSD.org      
security/py-paramiko1 lwhsu@FreeBSD.org      
security/py-ssh lwhsu@FreeBSD.org      
sysutils/hachoir-metadata lwhsu@FreeBSD.org      
sysutils/hachoir-subfile lwhsu@FreeBSD.org      
sysutils/hachoir-urwid lwhsu@FreeBSD.org      
sysutils/hachoir-wx lwhsu@FreeBSD.org      
textproc/cgrep lwhsu@FreeBSD.org      
textproc/p5-Vroom lwhsu@FreeBSD.org      
textproc/tokyodystopia lwhsu@FreeBSD.org      
www/mod_h264_streaming lwhsu@FreeBSD.org      
www/p5-Template-Toolkit-Simple lwhsu@FreeBSD.org      
www/py-blogofile lwhsu@FreeBSD.org      
www/py-clientform lwhsu@FreeBSD.org      
www/py-django-storages lwhsu@FreeBSD.org      
www/py-flup lwhsu@FreeBSD.org      
www/py-funkload lwhsu@FreeBSD.org      
www/py-httplib2 lwhsu@FreeBSD.org      
www/py-mechanize lwhsu@FreeBSD.org      
www/py-pyramid_rpc lwhsu@FreeBSD.org      
www/py-pysearch lwhsu@FreeBSD.org      
www/py-restclient lwhsu@FreeBSD.org      
www/py-webunit lwhsu@FreeBSD.org      
ports shown: 69   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.