Report created on Tue Mar 28 08:20:52 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/giggle ashish@FreeBSD.org      
devel/gtkparasite ashish@FreeBSD.org      
devel/libpthread-stubs ashish@FreeBSD.org      
devel/p5-Devel-REPL ashish@FreeBSD.org      
devel/p5-MooseX-Object-Pluggable ashish@FreeBSD.org      
devel/p5-Sepia ashish@FreeBSD.org      
devel/phpsh ashish@FreeBSD.org      
dns/nss_mdns ashish@FreeBSD.org      
dns/pdnsd ashish@FreeBSD.org      
editors/emacs ashish@FreeBSD.org      
editors/emacs-devel ashish@FreeBSD.org      
editors/emacs-nox11 ashish@FreeBSD.org      
graphics/frogr ashish@FreeBSD.org      
graphics/py-mcomix ashish@FreeBSD.org      
irc/ctrlproxy ashish@FreeBSD.org      
irc/irssi-fish ashish@FreeBSD.org      
irc/irssi-otr ashish@FreeBSD.org linker_error    
lang/rubinius ashish@FreeBSD.org      
lang/sagittarius-scheme ashish@FreeBSD.org      
mail/faces ashish@FreeBSD.org      
mail/p5-Email-Simple-FromHandle ashish@FreeBSD.org      
math/eukleides ashish@FreeBSD.org      
multimedia/msdl ashish@FreeBSD.org      
net-im/ejabberd ashish@FreeBSD.org      
security/git-crypt ashish@FreeBSD.org      
security/hotssh ashish@FreeBSD.org      
security/p5-Crypt-CFB ashish@FreeBSD.org      
security/p5-Crypt-Ctr ashish@FreeBSD.org      
security/p5-Crypt-DES_PP ashish@FreeBSD.org      
security/p5-Crypt-GOST ashish@FreeBSD.org      
security/p5-Crypt-GPG ashish@FreeBSD.org      
security/p5-Crypt-HCE_MD5 ashish@FreeBSD.org      
security/p5-Crypt-Khazad ashish@FreeBSD.org      
security/p5-Crypt-License ashish@FreeBSD.org      
security/p5-Crypt-Lite ashish@FreeBSD.org      
security/p5-Crypt-Loki97 ashish@FreeBSD.org      
security/p5-Crypt-MySQL ashish@FreeBSD.org      
security/p5-Crypt-SKey ashish@FreeBSD.org      
security/p5-Crypt-Salt ashish@FreeBSD.org      
security/p5-Crypt-Shark ashish@FreeBSD.org      
security/p5-Crypt-X509 ashish@FreeBSD.org      
security/p5-Digest-CRC ashish@FreeBSD.org      
security/p5-Digest-Crc32 ashish@FreeBSD.org      
security/p5-Digest-DJB ashish@FreeBSD.org      
security/p5-Digest-Elf ashish@FreeBSD.org      
security/p5-Digest-FNV ashish@FreeBSD.org      
security/p5-Digest-JHash ashish@FreeBSD.org      
security/p5-Digest-MD5-File ashish@FreeBSD.org      
security/p5-Digest-MD5-Reverse ashish@FreeBSD.org      
security/p5-Digest-ManberHash ashish@FreeBSD.org      
security/p5-Digest-Pearson ashish@FreeBSD.org      
security/p5-Digest-Pearson-PurePerl ashish@FreeBSD.org      
security/p5-Digest-Perl-MD4 ashish@FreeBSD.org      
security/p5-Digest-Perl-MD5 ashish@FreeBSD.org      
security/p5-Digest-SHA-PurePerl ashish@FreeBSD.org      
security/p5-Digest-SV1 ashish@FreeBSD.org      
sysutils/squashfs-tools ashish@FreeBSD.org      
textproc/p5-POD2-Base ashish@FreeBSD.org      
textproc/p5-PPIx-Regexp ashish@FreeBSD.org      
textproc/p5-Pod-Perldoc ashish@FreeBSD.org      
textproc/scim-bridge ashish@FreeBSD.org      
textproc/scim-bridge-qt4 ashish@FreeBSD.org      
www/xpi-conkeror ashish@FreeBSD.org      
www/xpi-foxyproxy ashish@FreeBSD.org      
www/xpi-pencil [B] ashish@FreeBSD.org      
x11-fonts/inconsolata-ttf ashish@FreeBSD.org      
x11-toolkits/hippo-canvas ashish@FreeBSD.org      
x11/hotwire-shell [B] ashish@FreeBSD.org      
x11/xpyb ashish@FreeBSD.org      
ports shown: 69   ports with build errors: 1 ports with outstanding PRs: 0  
ports with either build errors or PRs: 1

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.