Report created on Mon May 29 00:04:39 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
devel/cpp-netlib zi@FreeBSD.org      
devel/github-backup-utils zi@FreeBSD.org      
devel/p5-IO-Prompter zi@FreeBSD.org      
devel/py-qpid zi@FreeBSD.org      
devel/rubygem-webby zi@FreeBSD.org      
devel/uthash zi@FreeBSD.org      
dns/ares zi@FreeBSD.org      
dns/c-ares zi@FreeBSD.org      
dns/dnsflood zi@FreeBSD.org      
dns/gdnsd2 zi@FreeBSD.org      
dns/getdns zi@FreeBSD.org clang    
dns/p5-Net-DNS-Check zi@FreeBSD.org      
editors/le zi@FreeBSD.org linker_error    
irc/ratbox-respond zi@FreeBSD.org      
mail/p5-Email-Stuffer zi@FreeBSD.org      
mail/proxsmtp zi@FreeBSD.org      
misc/logsurfer zi@FreeBSD.org      
misc/nms zi@FreeBSD.org      
net-mgmt/jnettop zi@FreeBSD.org      
net-mgmt/nagios-check_email_delivery zi@FreeBSD.org      
net-mgmt/nagios-check_hp_bladechassis zi@FreeBSD.org      
net-mgmt/nagios-check_mysql_slave zi@FreeBSD.org      
net-mgmt/nagios-openldap-plugins zi@FreeBSD.org      
net-mgmt/nagtail zi@FreeBSD.org      
net-mgmt/net-snmp zi@FreeBSD.org configure_error    
net-mgmt/sdig zi@FreeBSD.org      
net-mgmt/snmp4nagios zi@FreeBSD.org      
net/daq zi@FreeBSD.org      
net/dhcpd-pools zi@FreeBSD.org      
net/exabgp zi@FreeBSD.org      
net/exaddos zi@FreeBSD.org      
net/freeradius2 zi@FreeBSD.org      
net/freeradius3 zi@FreeBSD.org      
net/hsflowd zi@FreeBSD.org ???    
net/isc-dhcp43-client zi@FreeBSD.org      
net/isc-dhcp43-relay zi@FreeBSD.org      
net/isc-dhcp43-server zi@FreeBSD.org      
net/mosh zi@FreeBSD.org      
net/nss-pam-ldapd zi@FreeBSD.org      
net/nss-pam-ldapd-sasl zi@FreeBSD.org      
net/ntraceroute zi@FreeBSD.org      
net/pwhois zi@FreeBSD.org      
net/vmware-vsphere-cli zi@FreeBSD.org      
security/clambc zi@FreeBSD.org configure_error
coredump
   
security/duo zi@FreeBSD.org configure_error    
security/hitch zi@FreeBSD.org      
security/kstart zi@FreeBSD.org      
security/openconnect zi@FreeBSD.org      
security/pam_krb5-rh zi@FreeBSD.org      
security/paperkey zi@FreeBSD.org      
security/seccure zi@FreeBSD.org      
security/snort zi@FreeBSD.org configure_error    
security/stunnel zi@FreeBSD.org linker_error    
security/truecrypt zi@FreeBSD.org      
sysutils/ipmitool zi@FreeBSD.org      
sysutils/msktutil zi@FreeBSD.org      
sysutils/osquery zi@FreeBSD.org      
sysutils/racktables zi@FreeBSD.org      
sysutils/userinfo zi@FreeBSD.org      
sysutils/vpnc-scripts zi@FreeBSD.org      
textproc/fex zi@FreeBSD.org      
textproc/py-elasticsearch-py zi@FreeBSD.org      
textproc/py-hypua2jamo zi@FreeBSD.org      
textproc/py-pyhwp zi@FreeBSD.org      
www/rubygem-nanoc zi@FreeBSD.org      
www/rubygem-tinymce-rails zi@FreeBSD.org      
ports shown: 66   ports with build errors: 8 ports with outstanding PRs: 0  
ports with either build errors or PRs: 8

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.