Report created on Tue May 23 03:08:48 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
astro/p5-ZConf-Weather vvelox@vvelox.net      
audio/p5-MP3-Tag-Utils vvelox@vvelox.net      
deskutils/p5-ZConf-BGSet vvelox@vvelox.net      
deskutils/p5-ZConf-Runner vvelox@vvelox.net      
deskutils/p5-ZConf-Runner-GUI-GTK vvelox@vvelox.net      
devel/p5-Chooser vvelox@vvelox.net      
devel/p5-Dir-Watch vvelox@vvelox.net      
devel/p5-IO-MultiPipe vvelox@vvelox.net      
devel/p5-ZConf-GUI vvelox@vvelox.net      
devel/p5-ZML vvelox@vvelox.net      
dns/p5-Net-DNS-RR-SRV-Helper vvelox@vvelox.net      
graphics/p5-Image-Size-FillFullSelect vvelox@vvelox.net      
graphics/p5-Imager-AverageGray vvelox@vvelox.net      
mail/p5-Mail-Cache vvelox@vvelox.net      
mail/p5-Mail-IMAPTalk-MailCache vvelox@vvelox.net      
mail/p5-Net-Server-Mail vvelox@vvelox.net      
mail/p5-ZConf-Mail vvelox@vvelox.net      
net/p5-Net-LDAP-AutoDNs vvelox@vvelox.net      
net/p5-Net-LDAP-AutoServer vvelox@vvelox.net      
net/p5-Net-LDAP-Express vvelox@vvelox.net      
net/p5-Net-LDAP-LDAPhash vvelox@vvelox.net      
net/p5-Net-LDAP-Makepath vvelox@vvelox.net      
net/p5-Net-LDAP-posixAccount vvelox@vvelox.net      
net/p5-Net-LDAP-posixGroup vvelox@vvelox.net      
net/p5-Net-WhitePages vvelox@vvelox.net      
net/p5-Phone-Info vvelox@vvelox.net      
net/p5-ZConf vvelox@vvelox.net      
net/p5-ZConf-Bookmarks vvelox@vvelox.net      
ports-mgmt/p5-FreeBSD-Ports-INDEXhash vvelox@vvelox.net      
security/p5-Net-Server-Mail-ESMTP-AUTH vvelox@vvelox.net      
security/snortreport vvelox@vvelox.net      
shells/shell-include vvelox@vvelox.net      
sysutils/p5-Plugtools vvelox@vvelox.net      
sysutils/p5-Plugtools-Plugins-HomeOU vvelox@vvelox.net      
sysutils/p5-Samba-SIDhelper vvelox@vvelox.net      
sysutils/p5-Sys-Group-GIDhelper vvelox@vvelox.net      
sysutils/p5-Sys-User-UIDhelper vvelox@vvelox.net      
sysutils/p5-ZConf-Cron vvelox@vvelox.net      
textproc/p5-Text-SpellChecker-GUI vvelox@vvelox.net      
www/p5-Gtk2-WebKit vvelox@vvelox.net      
www/p5-Toader vvelox@vvelox.net      
www/p5-ZConf-RSS vvelox@vvelox.net      
www/p5-ZConf-RSS-GUI-GTK vvelox@vvelox.net      
x11-fm/p5-PerlFM vvelox@vvelox.net      
x11-toolkits/p5-Gtk2-Chmod vvelox@vvelox.net      
x11-toolkits/p5-Gtk2-PathButtonBar vvelox@vvelox.net      
x11/p5-X11-Resolution vvelox@vvelox.net      
x11/roxbg vvelox@vvelox.net      
ports shown: 48   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.