Report created on Thu Aug 25 20:13:43 2016. back to main menu

For explanatory information and summary details, see the notes below.

portname maintainer build error logs Problem Reports Responsible
archivers/ruby-zip ruby@FreeBSD.org      
audio/aureal-kmod c.kworr@gmail.com      
audio/ruby-xmms2 ruby@FreeBSD.org      
audio/ufmcontrol-i18n nivit@FreeBSD.org      
audio/xmms-openspc ehaupt@FreeBSD.org      
biology/molden pi@FreeBSD.org fetch    
databases/postgresql-plruby knu@FreeBSD.org      
databases/rubygem-dm-devise ruby@FreeBSD.org      
deskutils/gnome-shell-extension-backslide gnome@FreeBSD.org      
devel/erlang-exmpp olgeni@FreeBSD.org      
devel/gaphor ports@FreeBSD.org      
devel/git-lfs kuriyama@FreeBSD.org      
devel/go-tools cs@FreeBSD.org      
devel/libdict rodrigo@FreeBSD.org      
devel/monodevelop mono@FreeBSD.org      
devel/openvex bacon4000@gmail.com      
devel/pig demon@FreeBSD.org      
devel/py-re2 edwardchuang@gmail.com      
devel/py-snack python@FreeBSD.org      
devel/ruby-langscan tota@FreeBSD.org      
devel/ruby-rbison ruby@FreeBSD.org      
devel/rubygem-devise-async ruby@FreeBSD.org      
devel/rubygem-devise-async-rails4 ruby@FreeBSD.org      
devel/rubygem-ditz kuriyama@FreeBSD.org      
dns/dns_balance portmaster@BSDforge.com      
editors/mg darcsis@gmail.com      
emulators/doscmd ports@FreeBSD.org      
emulators/kqemu-kmod ports@FreeBSD.org      
ftp/bareftp ports@FreeBSD.org      
ftp/curl-hiphop mm@FreeBSD.org      
games/vegastrike ports@FreeBSD.org clang    
graphics/gnash ports@FreeBSD.org      
japanese/kterm hrs@FreeBSD.org      
lang/beignet x11@FreeBSD.org      
lang/libjit ports@FreeBSD.org clang    
lang/maude ports@FreeBSD.org      
lang/rubinius ashish@FreeBSD.org      
lang/spark marino@FreeBSD.org      
lang/swift swills@FreeBSD.org ???    
mail/lens tota@FreeBSD.org      
mail/mixmaster cs@FreeBSD.org      
math/R-cran-SuppDists ports@FreeBSD.org      
math/emc2 ports@FreeBSD.org fetch    
math/libR jrm@ftfl.ca distinfo_update    
math/libRmath jrm@ftfl.ca      
math/octave-forge-ad stephen@FreeBSD.org      
math/octave-forge-dicom stephen@FreeBSD.org      
math/octave-forge-octgpr stephen@FreeBSD.org      
math/octave-forge-pdb stephen@FreeBSD.org      
math/octave-forge-secs2d stephen@FreeBSD.org      
math/octave-forge-spline-gcvspl stephen@FreeBSD.org      
math/octave-forge-xraylib stephen@FreeBSD.org      
math/py-pyfst demon@FreeBSD.org      
misc/teslams bmah@FreeBSD.org      
net-im/skype4 johannes@perceivon.net      
net-mgmt/nat ports@FreeBSD.org fetch    
net-p2p/digitalcoin myst3r10n@rocketmail.com      
net-p2p/gnunet ports@FreeBSD.org      
net/cyphesis oliver@FreeBSD.org      
net/dosdetector msciciel@dark-zone.eu      
net/gpxe gk.freebsd@googlemail.com      
net/openospfd rea@FreeBSD.org      
net/ruby-dict ruby@FreeBSD.org      
print/lilypond-devel ports@FreeBSD.org      
print/musixtex ports@FreeBSD.org ???    
print/py-reportlab2 kozlov.sergey.404@gmail.com      
security/lsh johans@FreeBSD.org      
security/massh ports@FreeBSD.org      
security/ruby-password ruby@FreeBSD.org      
security/titus feld@FreeBSD.org      
sysutils/apt koobs@FreeBSD.org      
sysutils/freefilesync ports@FreeBSD.org ???    
sysutils/gosa ports@FreeBSD.org      
textproc/aiksaurus-gtk gnome@FreeBSD.org      
textproc/py-cloud_sptheme ports@FreeBSD.org      
textproc/rubygem-string-scrub kuriyama@FreeBSD.org      
www/fira-webfont ports@FreeBSD.org      
www/hydra ports@FreeBSD.org      
www/offline-npm cpm@FreeBSD.org      
www/pear-Services_SharedBook ports@FreeBSD.org      
www/samidare tota@FreeBSD.org      
www/wml rodrigo@FreeBSD.org      
x11-themes/kde-icons-cezanne ports@FreeBSD.org      
x11-themes/kde-icons-sky ports@FreeBSD.org      
x11-toolkits/py-traitsbackendwx jacob.frelinger@duke.edu      
x11-toolkits/qtada marino@FreeBSD.org      
x11/deforaos-panel olivier@FreeBSD.org      
ports shown: 87   ports with build errors: 9 ports with outstanding PRs: 0  
ports with either build errors or PRs: 9

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.