Report created on Thu Mar 26 23:47:51 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-zip 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      
databases/pydbdesigner xride@FreeBSD.org      
deskutils/cdcat 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/p5-Cdk ports@FreeBSD.org      
devel/rubygem-debugger ports@FreeBSD.org      
devel/rubygem-igraph ruby@FreeBSD.org      
devel/rubygem-rcov skreuzer@FreeBSD.org      
devel/scala-ide ale@FreeBSD.org      
devel/subclipse ports@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      
emulators/xzx ports@FreeBSD.org fetch    
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/ruby-gd dinoex@FreeBSD.org      
graphics/sng robak@FreeBSD.org      
japanese/netype mutoh@openedu.org      
japanese/p5-Text-MeCab fmysh@iijmio-mail.jp      
java/commonclipse zhoushuqun@gmail.com      
java/eclipse-RDT ports@FreeBSD.org      
java/eclipse-aptana nivit@FreeBSD.org      
java/eclipse-aptana-radrails ports@FreeBSD.org      
java/eclipse-aptana2 nivit@FreeBSD.org      
java/eclipse-checkstyle ports@FreeBSD.org      
java/eclipse-datatools ljboiler@gmail.com      
java/eclipse-emf kamikaze@bsdforen.de      
java/eclipse-examples ports@FreeBSD.org      
java/eclipse-gef zhoushuqun@gmail.com      
java/eclipse-gef-examples ports@FreeBSD.org      
java/eclipse-hibernatetools ports@FreeBSD.org      
java/eclipse-jad ale@FreeBSD.org      
java/eclipse-langpack ports@FreeBSD.org      
java/eclipse-pmd ports@FreeBSD.org      
java/eclipse-propedit zhoushuqun@gmail.com      
java/eclipse-sqlexplorer ports@FreeBSD.org      
java/eclipse-sysdeo-tomcat ports@FreeBSD.org      
java/eclipse-uml ports@FreeBSD.org      
java/eclipse-vep ports@FreeBSD.org      
java/eclipse-vep-examples ports@FreeBSD.org      
java/eclipse-viplugin ports@FreeBSD.org      
java/eclipse-webtools ale@FreeBSD.org      
lang/pure lichray@gmail.com      
mail/mail-notification ports@FreeBSD.org      
mail/maildirsync bofh@FreeBSD.org      
mail/p5-MIME-Fast perl@FreeBSD.org      
mail/qar-bufo vvelox@vvelox.net      
math/sage stephen@FreeBSD.org   198893: math/sage : fails to build on FreeBSD 10 stephen@FreeBSD.org
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/cyphesis oliver@FreeBSD.org      
net/gpxe gk.freebsd@googlemail.com      
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   198302: net/ntopng: Doesn't build on -HEAD 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      
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      
www/diamanda ports@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: 98   ports with build errors: 2 ports with outstanding PRs: 6  
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.