Report created on Mon May 29 21:00:08 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/mysql-connector-java matthew@FreeBSD.org      
databases/mytop matthew@FreeBSD.org      
databases/pg_citus matthew@FreeBSD.org      
databases/pgbarman matthew@FreeBSD.org      
databases/pgespresso matthew@FreeBSD.org      
databases/pglogical matthew@FreeBSD.org      
databases/pgreplay matthew@FreeBSD.org      
databases/phpmyadmin matthew@FreeBSD.org      
databases/py-agate-sql matthew@FreeBSD.org      
deskutils/p5-Data-ICal-DateTime matthew@FreeBSD.org      
devel/libee matthew@FreeBSD.org      
devel/libestr matthew@FreeBSD.org      
devel/liblogging matthew@FreeBSD.org      
devel/librelp matthew@FreeBSD.org      
devel/p5-Date-Extract matthew@FreeBSD.org      
devel/p5-Role-Basic matthew@FreeBSD.org      
devel/p5-Set-Tiny matthew@FreeBSD.org      
devel/p5-Symbol-Global-Name matthew@FreeBSD.org      
devel/rubygem-svn2git matthew@FreeBSD.org      
graphics/py-leather matthew@FreeBSD.org      
mail/p5-Email-Address-List matthew@FreeBSD.org      
mail/p5-Mail-OpenDKIM matthew@FreeBSD.org      
mail/p5-Test-Email matthew@FreeBSD.org      
mail/sa-utils matthew@FreeBSD.org      
math/p5-Math-Fleximal matthew@FreeBSD.org      
misc/p5-Business-Hours matthew@FreeBSD.org      
net-mgmt/nagios-check_postgres matthew@FreeBSD.org      
net/phpldapadmin matthew@FreeBSD.org      
ports-mgmt/p5-FreeBSD-Portindex matthew@FreeBSD.org      
ports-mgmt/wanted-ports matthew@FreeBSD.org      
security/apg matthew@FreeBSD.org      
sysutils/p5-Log-Syslog-Constants matthew@FreeBSD.org      
sysutils/p5-Log-Syslog-Fast matthew@FreeBSD.org      
sysutils/rsyslog8 matthew@FreeBSD.org      
sysutils/rubygem-hiera-file matthew@FreeBSD.org      
textproc/py-agate matthew@FreeBSD.org      
textproc/py-agate-dbf matthew@FreeBSD.org      
textproc/py-agate-excel matthew@FreeBSD.org      
textproc/py-awesome-slugify matthew@FreeBSD.org      
textproc/py-csvkit matthew@FreeBSD.org      
textproc/py-dbfread matthew@FreeBSD.org      
textproc/py-python-slugify matthew@FreeBSD.org      
textproc/sphinxsearch matthew@FreeBSD.org      
www/p5-Plack-Middleware-Test-StashWarnings matthew@FreeBSD.org      
www/p5-RT-Authen-ExternalAuth matthew@FreeBSD.org      
www/p5-RT-Extension-LDAPImport matthew@FreeBSD.org      
www/p5-RT-Extension-MandatoryOnTransition matthew@FreeBSD.org      
www/p5-RT-Extension-SLA matthew@FreeBSD.org      
www/p5-RTx-Calendar matthew@FreeBSD.org      
www/p5-WWW-Salesforce matthew@FreeBSD.org      
www/rt42 matthew@FreeBSD.org      
www/trac-ldap matthew@FreeBSD.org      
www/trac-ldapauthstore matthew@FreeBSD.org      
x11-fonts/gentium-basic matthew@FreeBSD.org      
x11-fonts/gentium-plus matthew@FreeBSD.org      
ports shown: 55   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.