Report created on Thu Mar 5 06:35:42 2015. back to main menu

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

portname maintainer build error logs Problem Reports Responsible
archivers/ruby-lha ruby@FreeBSD.org   195268: [patch] archivers/ruby-lha: fix build for ruby 2.0 ruby@FreeBSD.org
audio/aureal-kmod c.kworr@gmail.com      
audio/mp3splt-gtk beyert@cs.ucr.edu      
audio/padevchooser romain@FreeBSD.org      
audio/raproxy ports@FreeBSD.org      
audio/xmms-openspc ehaupt@FreeBSD.org      
biology/platon ports@FreeBSD.org      
biology/seaview bofh@FreeBSD.org      
biology/tinker ports@FreeBSD.org fetch    
cad/cider ports@FreeBSD.org      
databases/gtksql ports@FreeBSD.org      
databases/mariadb-client dgeo@centrale-marseille.fr      
databases/mariadb-server dgeo@centrale-marseille.fr   197679: databases/mariadb-server builds on FreeBSD 10.1-RELEASE freebsd-ports-bugs@FreeBSD.org
databases/pydbdesigner xride@FreeBSD.org      
databases/tora ports@FreeBSD.org      
deskutils/deskbar-applet gnome@FreeBSD.org      
deskutils/gimmie pneumann@gmail.com      
deskutils/glipper ports@FreeBSD.org      
deskutils/gnochm ports@FreeBSD.org      
deskutils/hamster-applet gnome@FreeBSD.org      
deskutils/kupfer ports@FreeBSD.org      
deskutils/ontv gnome@FreeBSD.org      
deskutils/timer-applet ports@FreeBSD.org      
devel/frama-c bf@FreeBSD.org cluster    
devel/lua-gettext ports@FreeBSD.org   197400: devel/lua-gettext UNBREAK - FIXES MASTER_SITES freebsd-ports-bugs@FreeBSD.org
devel/lua-pty ports@FreeBSD.org   197401: devel/lua-pty UNBREAK; FIXES MASTER_SITES freebsd-ports-bugs@FreeBSD.org
devel/p5-Cdk ports@FreeBSD.org      
devel/rubygem-igraph ruby@FreeBSD.org      
devel/rubygem-rcov skreuzer@FreeBSD.org      
devel/xtla ports@FreeBSD.org      
editors/scribes ports@FreeBSD.org      
emulators/kqemu-kmod nox@FreeBSD.org      
emulators/linux_base-gentoo-stage3 ports@FreeBSD.org      
emulators/linux_dist-gentoo-stage3 ports@FreeBSD.org      
games/gtkradiant danfe@FreeBSD.org      
games/linux-candycruncher-demo mva@FreeBSD.org      
games/linux-coldwar-demo mva@FreeBSD.org      
games/linux-gorky17-demo mva@FreeBSD.org      
games/linux-hdb-demo mva@FreeBSD.org      
games/linux-majesty-demo mva@FreeBSD.org      
games/py-pychess ports@FreeBSD.org      
games/spring amdmi3@FreeBSD.org      
games/wmfortune ports@FreeBSD.org      
graphics/gnash ports@FreeBSD.org      
graphics/kuickshow-kde4 kde@FreeBSD.org      
graphics/opengtl avilla@FreeBSD.org      
graphics/p5-Image-Scale atkin901@gmail.com   197958: [MAINTAINER] graphics/p5-Image-Scale: Fix BROKEN disable gif support freebsd-ports-bugs@FreeBSD.org
graphics/sng robak@FreeBSD.org      
graphics/xfpovray ports@FreeBSD.org      
japanese/netype mutoh@openedu.org      
japanese/p5-Text-MeCab fmysh@iijmio-mail.jp      
lang/pure lichray@gmail.com      
mail/mail-notification ports@FreeBSD.org cluster    
mail/maildirsync bofh@FreeBSD.org      
mail/p5-MIME-Fast perl@FreeBSD.org      
mail/qar-bufo vvelox@vvelox.net      
multimedia/arista swills@FreeBSD.org      
multimedia/bombono ports@FreeBSD.org linker_error    
multimedia/subtitleeditor multimedia@FreeBSD.org      
net-im/skype4 xmj@chaot.net   193877: net-im/skype4 freebsd-ports-bugs@FreeBSD.org
net-mgmt/netxms bofh@FreeBSD.org      
net-mgmt/tcptrack squat@squat.no   191902: [update] net-mgmt/tcptrack doesn't build and when patched, segfaults pi@FreeBSD.org
net/cyphesis oliver@FreeBSD.org      
net/gpxe gk.freebsd@googlemail.com      
net/netselect ports@FreeBSD.org      
net/nocatsplash ports@FreeBSD.org   197495: net/nocatsplash FIXES USERS GUIDS MASTER_SITES, REMOVES BROKEN freebsd-ports-bugs@FreeBSD.org
net/ntopng bofh@FreeBSD.org      
net/openospfd rea@FreeBSD.org      
net/service-discovery-applet gnome@FreeBSD.org      
ports-mgmt/gnome-packagekit gnome@FreeBSD.org      
print/gnome-specimen swills@FreeBSD.org      
print/sgf2tex spcoltri@omcl.org      
science/meep devel@stasyan.com      
science/py-scimath wen@FreeBSD.org   197589: science/py-scimath: Fix (add) dependency, Mark UnBROKEN wen@FreeBSD.org
security/arirang ports@FreeBSD.org      
security/p5-Crypt-GOST ashish@FreeBSD.org      
security/p5-Crypt-TEA skreuzer@FreeBSD.org      
sysutils/pesign trasz@FreeBSD.org      
sysutils/puppet27 swills@FreeBSD.org   194549: sysutils/puppet27 2.7.26_1 (some kind of ruby19 complaint) swills@FreeBSD.org
sysutils/py-salt-api christer.edwards@gmail.com      
textproc/aiksaurus-gtk gnome@FreeBSD.org      
textproc/p5-Groonga-API kuriyama@FreeBSD.org      
textproc/pecl-cld gasol.wu@gmail.com      
textproc/refdb ohartman@zedat.fu-berlin.de missing_LDFLAGS    
www/diamanda ports@FreeBSD.org      
x11-toolkits/py-kivy dbn@FreeBSD.org      
x11-wm/e-module-diskio gblach@FreeBSD.org      
x11-wm/ede ports@FreeBSD.org   193394: x11-wm/ede/: ede-keyboard-conf was compiled without XKB extension. freebsd-ports-bugs@FreeBSD.org
ports shown: 88   ports with build errors: 5 ports with outstanding PRs: 11  
ports with either build errors or PRs: 16

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.