Report created on Fri May 26 19:01:05 2017. back to main menu

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

portname maintainer build error logs Problem Reports Responsible
astro/gmapcatcher kevlo@FreeBSD.org      
astro/viking koalative@gmail.com      
audio/ardour danfe@FreeBSD.org      
audio/gigedit ports@FreeBSD.org      
audio/gnomoradio ports@FreeBSD.org      
audio/gspeakers ports@FreeBSD.org      
audio/linux-neroaaccodec ports@FreeBSD.org fetch    
audio/sooperlooper ports@FreeBSD.org bad_C++_code    
audio/tclmidi ports@FreeBSD.org      
biology/biojava ports@FreeBSD.org      
biology/molden jmd@FreeBSD.org fetch    
cad/linuxcnc-devel trasz@FreeBSD.org      
cad/repsnapper martin.dieringer@gmx.de      
chinese/libtabe ports@FreeBSD.org      
comms/qtel hamradio@FreeBSD.org      
comms/svxlink hamradio@FreeBSD.org      
databases/cassandra2 admins@perceptyx.com      
databases/elixir-ecto_migrate olgeni@FreeBSD.org      
databases/glom kwm@FreeBSD.org      
databases/mysql-q4m knu@FreeBSD.org      
databases/postgresql-plruby knu@FreeBSD.org      
deskutils/easystroke ports@FreeBSD.org      
devel/arduino-glcd leres@ee.lbl.gov      
devel/art virtual.lark@gmail.com      
devel/cl-cffi-sbcl olgeni@FreeBSD.org      
devel/cld demon@FreeBSD.org      
devel/dwarves cem@FreeBSD.org      
devel/gdb66 mi@aldan.algebra.com      
devel/guikachu ports@FreeBSD.org bad_C++_code    
devel/libical-glib gnome@FreeBSD.org      
devel/pig demon@FreeBSD.org      
devel/pinba_engine raven428@gmail.com      
devel/py-InlineEgg sbz@FreeBSD.org      
devel/py-event ports@FreeBSD.org      
devel/py-protocols-devel wen@FreeBSD.org      
devel/ruby-ncurses saurbier@math.uni-bielefeld.de      
devel/rubygem-ditz kuriyama@FreeBSD.org      
emulators/raine ports@FreeBSD.org linker_error    
games/cheech ports@FreeBSD.org      
games/crafty johans@FreeBSD.org      
games/ember oliver@FreeBSD.org      
games/freedoko ports@FreeBSD.org      
games/gish-demo ports@FreeBSD.org fetch    
games/kye ports@FreeBSD.org      
games/libretro-cores yuri@rawbw.com bad_C++_code    
games/linux-nwnclient scf@FreeBSD.org fetch    
games/lordsawar ports@FreeBSD.org      
games/plee-the-bear amdmi3@FreeBSD.org      
games/xroach ports@FreeBSD.org      
graphics/gimmage portmaster@bsdforge.com      
graphics/gmt ports@FreeBSD.org      
graphics/py-graph-dot demon@FreeBSD.org      
graphics/synfigstudio woodsb02@FreeBSD.org      
irc/rbot bdrewery@FreeBSD.org      
japanese/jd townwear@gmail.com      
lang/bigloo ports@FreeBSD.org      
lang/gcl ports@FreeBSD.org missing_header    
mail/lens tota@FreeBSD.org      
mail/libmapi kwm@FreeBSD.org      
math/asir2000 ports@FreeBSD.org      
math/bargraph dereckson@gmail.com      
misc/fortune-mod-culmea-culmilor ports@FreeBSD.org      
misc/fortune-mod-ferengi_rules_of_acquisition ports@FreeBSD.org      
misc/xyzcmd vg@FreeBSD.org      
multimedia/avbin amdmi3@FreeBSD.org      
multimedia/banshee mono@FreeBSD.org      
multimedia/bombono ports@FreeBSD.org      
multimedia/librespot mmokhi@FreeBSD.org      
multimedia/plexhometheater woodsb02@FreeBSD.org      
net/p5-Filesys-SmbClient perl@FreeBSD.org      
net/pmf ports@FreeBSD.org      
russian/fortuneru obezpalko@gmail.com      
security/bdc ports@FreeBSD.org      
security/mdcrack lasg@lasg.dk      
security/pond ports@FreeBSD.org      
security/py-pyptlib cs@FreeBSD.org      
security/py-xmlsec ports@FreeBSD.org compiler_error    
security/radamsa jau@iki.fi      
security/samba-virusfilter kuriyama@FreeBSD.org      
security/tclgpg mp39590@gmail.com      
shells/ambit ports@FreeBSD.org      
sysutils/flyback ports@FreeBSD.org      
sysutils/passwordsafe brnrd@FreeBSD.org      
textproc/ocaml-pxp ports@FreeBSD.org      
textproc/ruby-sary ruby@FreeBSD.org      
www/py-octoprint bsdports@kyle-evans.net      
www/py-utidy ports@FreeBSD.org      
www/samidare tota@FreeBSD.org      
www/xpi-noscript gecko@FreeBSD.org      
x11-fonts/alfont nemysis@FreeBSD.org      
x11-themes/kde-icons-dark-glass ports@FreeBSD.org      
x11-themes/kde-icons-icosx ports@FreeBSD.org      
x11-themes/kde-icons-umicons ports@FreeBSD.org      
x11-toolkits/libgnomeprintuimm bland@FreeBSD.org      
x11-wm/gcompmgr ports@FreeBSD.org      
ports shown: 95   ports with build errors: 10 ports with outstanding PRs: 0  
ports with either build errors or PRs: 10

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.