Report created on Tue Sep 26 09:11:41 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
archivers/erlang-snappy vanilla@FreeBSD.org      
archivers/snappy vanilla@FreeBSD.org      
chinese/gcin vanilla@FreeBSD.org      
chinese/gcin-gtk3 vanilla@FreeBSD.org      
chinese/gcin-qt4 vanilla@FreeBSD.org      
chinese/gcin-qt5 vanilla@FreeBSD.org      
comms/py-gammu vanilla@FreeBSD.org      
converters/erlang-base64url vanilla@FreeBSD.org      
converters/lua-iconv vanilla@FreeBSD.org      
databases/elixir-exredis vanilla@FreeBSD.org      
databases/elixir-mongo vanilla@FreeBSD.org      
databases/p5-LMDB_File vanilla@FreeBSD.org      
databases/postgresql-plv8js vanilla@FreeBSD.org      
devel/elixir-bson vanilla@FreeBSD.org      
devel/elixir-coverex vanilla@FreeBSD.org      
devel/elixir-excoveralls vanilla@FreeBSD.org      
devel/grpc vanilla@FreeBSD.org      
devel/jansson vanilla@FreeBSD.org      
devel/mq4cpp vanilla@FreeBSD.org      
devel/pecl-grpc vanilla@FreeBSD.org      
devel/pecl-propro vanilla@FreeBSD.org      
devel/pecl-raphf vanilla@FreeBSD.org      
devel/pecl-swoole vanilla@FreeBSD.org ???
manpage
   
devel/py-google-apputils vanilla@FreeBSD.org      
devel/py-grpcio vanilla@FreeBSD.org      
devel/spdlog vanilla@FreeBSD.org ???
new_compiler_error
   
graphics/libqrencode vanilla@FreeBSD.org      
graphics/p5-Color-Calc vanilla@FreeBSD.org      
graphics/pecl-qrencode vanilla@FreeBSD.org      
misc/rump vanilla@FreeBSD.org      
net/elixir-kafka_ex vanilla@FreeBSD.org      
net/elixir-oauth2 vanilla@FreeBSD.org      
net/p5-Net-TacacsPlus vanilla@FreeBSD.org      
security/elixir-jose vanilla@FreeBSD.org      
security/erlang-jose vanilla@FreeBSD.org      
security/p5-CryptX vanilla@FreeBSD.org      
textproc/google-ctemplate vanilla@FreeBSD.org      
textproc/pecl-ctemplate vanilla@FreeBSD.org      
textproc/py-sphinxcontrib-fulltoc vanilla@FreeBSD.org      
www/elixir-joken vanilla@FreeBSD.org      
www/p5-Test-Nginx vanilla@FreeBSD.org      
www/varnish-libvmod-awsrest vanilla@FreeBSD.org      
ports shown: 42   ports with build errors: 2 ports with outstanding PRs: 0  
ports with either build errors or PRs: 2

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.