Report created on Sat Mar 25 10:09:05 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
comms/conserver cy@FreeBSD.org      
deskutils/plan cy@FreeBSD.org      
devel/libol cy@FreeBSD.org      
devel/mkcmd cy@FreeBSD.org      
devel/msrc0 cy@FreeBSD.org      
devel/rcs57 cy@FreeBSD.org      
devel/xxgdb cy@FreeBSD.org      
ftp/llnlxdir cy@FreeBSD.org      
ftp/llnlxftp cy@FreeBSD.org      
ftp/mirror cy@FreeBSD.org      
graphics/qxv cy@FreeBSD.org      
graphics/sane-epkowa cy@FreeBSD.org      
graphics/xpdf cy@FreeBSD.org      
japanese/plan cy@FreeBSD.org      
lang/dmd1 cy@FreeBSD.org      
lang/dmd2 cy@FreeBSD.org linker_error
new_compiler_error
   
mail/exmh2 cy@FreeBSD.org      
mail/heirloom-mailx cy@FreeBSD.org      
mail/nmh cy@FreeBSD.org      
misc/tkcron cy@FreeBSD.org      
net-mgmt/grepip cy@FreeBSD.org      
net/44bsd-rdist cy@FreeBSD.org      
net/fspclient cy@FreeBSD.org      
net/ntp cy@FreeBSD.org      
net/ntp-devel cy@FreeBSD.org      
net/pipsecd cy@FreeBSD.org      
net/rdist6 cy@FreeBSD.org      
net/tcpview cy@FreeBSD.org      
net/vtun cy@FreeBSD.org      
print/xpp cy@FreeBSD.org      
security/aide cy@FreeBSD.org      
security/bcwipe cy@FreeBSD.org      
security/cops cy@FreeBSD.org      
security/cracklib cy@FreeBSD.org      
security/fwanalog cy@FreeBSD.org      
security/fwbuilder cy@FreeBSD.org      
security/fwlogwatch cy@FreeBSD.org      
security/ipfmeta cy@FreeBSD.org      
security/krb5 cy@FreeBSD.org      
security/krb5-113 cy@FreeBSD.org      
security/krb5-114 cy@FreeBSD.org      
security/krb5-115 cy@FreeBSD.org      
security/krb5-appl cy@FreeBSD.org      
security/p5-File-KeePass-Agent cy@FreeBSD.org      
security/pam_krb5 cy@FreeBSD.org      
security/py-cracklib cy@FreeBSD.org      
security/racoon2 cy@FreeBSD.org      
security/tripwire cy@FreeBSD.org      
security/tripwire-131 cy@FreeBSD.org      
security/tripwire12 cy@FreeBSD.org      
shells/44bsd-csh cy@FreeBSD.org      
sysutils/44bsd-more cy@FreeBSD.org      
sysutils/am-utils cy@FreeBSD.org      
sysutils/cfengine cy@FreeBSD.org      
sysutils/cfengine-masterfiles cy@FreeBSD.org      
sysutils/cfengine-masterfiles310 cy@FreeBSD.org      
sysutils/cfengine-masterfiles36 cy@FreeBSD.org      
sysutils/cfengine-masterfiles37 cy@FreeBSD.org      
sysutils/cfengine-masterfiles38 cy@FreeBSD.org      
sysutils/cfengine-masterfiles39 cy@FreeBSD.org      
sysutils/cfengine22 cy@FreeBSD.org      
sysutils/cfengine310 cy@FreeBSD.org      
sysutils/cfengine32 cy@FreeBSD.org      
sysutils/cfengine33 cy@FreeBSD.org      
sysutils/cfengine34 cy@FreeBSD.org      
sysutils/cfengine35 cy@FreeBSD.org      
sysutils/cfengine36 cy@FreeBSD.org      
sysutils/cfengine37 cy@FreeBSD.org      
sysutils/cfengine38 cy@FreeBSD.org      
sysutils/cfengine39 cy@FreeBSD.org      
sysutils/curly cy@FreeBSD.org      
sysutils/disktool cy@FreeBSD.org      
sysutils/doinkd cy@FreeBSD.org      
sysutils/eventlog cy@FreeBSD.org      
sysutils/hdrecover cy@FreeBSD.org      
sysutils/heirloom cy@FreeBSD.org      
sysutils/ipsc cy@FreeBSD.org      
sysutils/nut cy@FreeBSD.org      
sysutils/screen cy@FreeBSD.org      
sysutils/syslog-ng cy@FreeBSD.org ???    
sysutils/syslog-ng-devel cy@FreeBSD.org ???    
sysutils/syslog-ng-incubator cy@FreeBSD.org      
sysutils/syslog-ng36 cy@FreeBSD.org ???    
sysutils/syslog-ng37 cy@FreeBSD.org ???    
sysutils/xdu cy@FreeBSD.org      
sysutils/zetaback cy@FreeBSD.org      
www/webcopy cy@FreeBSD.org      
x11-clocks/xalarm cy@FreeBSD.org      
x11-toolkits/Xmt cy@FreeBSD.org      
x11-toolkits/open-motif cy@FreeBSD.org      
x11-toolkits/slingshot cy@FreeBSD.org      
x11-toolkits/xview cy@FreeBSD.org      
x11-toolkits/xview-clients cy@FreeBSD.org      
x11-wm/fvwm2 cy@FreeBSD.org      
x11-wm/olvwm cy@FreeBSD.org      
x11/props cy@FreeBSD.org      
x11/xascii cy@FreeBSD.org      
x11/xcut cy@FreeBSD.org      
x11/xforward cy@FreeBSD.org      
x11/xvattr cy@FreeBSD.org      
ports shown: 100   ports with build errors: 5 ports with outstanding PRs: 0  
ports with either build errors or PRs: 5

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.