Report created on Mon Oct 20 21:20:36 2014. back to main menu

NOTE: as of 20140601, GNATS has been deprecated. Until portsmon can catch up, expect the PR data to be stale.

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/p5-Audio-FLAC-Header lippe@FreeBSD.org      
databases/mysqlreport lippe@FreeBSD.org      
databases/mysqlsla lippe@FreeBSD.org      
databases/p5-DBD-Mock lippe@FreeBSD.org      
databases/p5-Test-DatabaseRow lippe@FreeBSD.org      
devel/jep lippe@FreeBSD.org      
devel/p5-Class-Std lippe@FreeBSD.org      
devel/p5-Devel-SimpleTrace lippe@FreeBSD.org      
devel/p5-Exception-Class-TryCatch lippe@FreeBSD.org      
devel/p5-ExtUtils-Manifest lippe@FreeBSD.org      
devel/p5-Geo-ShapeFile lippe@FreeBSD.org      
devel/p5-Module-Refresh lippe@FreeBSD.org      
devel/p5-Test-Distribution lippe@FreeBSD.org      
devel/p5-Test-Kwalitee lippe@FreeBSD.org      
devel/p5-Test-LectroTest lippe@FreeBSD.org      
devel/p5-Test-NoWarnings lippe@FreeBSD.org      
devel/p5-Test-Portability-Files lippe@FreeBSD.org      
devel/p5-Test-YAML-Meta lippe@FreeBSD.org      
devel/p5-Tie-ToObject lippe@FreeBSD.org      
devel/premake lippe@FreeBSD.org      
devel/st lippe@FreeBSD.org      
graphics/ocrad lippe@FreeBSD.org      
graphics/p5-Geo-Proj4 lippe@FreeBSD.org      
mail/simscan lippe@FreeBSD.org      
misc/ttyrec lippe@FreeBSD.org      
net-mgmt/weathermap lippe@FreeBSD.org      
net/p5-Net-Google-AuthSub lippe@FreeBSD.org      
net/zsync lippe@FreeBSD.org      
security/p5-Business-PayPal-EWP lippe@FreeBSD.org      
sysutils/p5-Probe-Perl lippe@FreeBSD.org      
textproc/p5-Excel-Template lippe@FreeBSD.org      
textproc/p5-Getopt-Lucid lippe@FreeBSD.org      
www/p5-CGI-Application-Plugin-DBH lippe@FreeBSD.org      
www/p5-CGI-Application-Plugin-HTDot lippe@FreeBSD.org      
www/p5-CGI-Application-Plugin-ValidateRM lippe@FreeBSD.org      
www/p5-HTML-Template-Pluggable lippe@FreeBSD.org      
ports shown: 36   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 GNATS 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 GNATS 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 gnatsQueryUtils.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.