Report created on Tue Aug 22 15:05:24 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
audio/libopenspc kwm@FreeBSD.org      
databases/glom [B] kwm@FreeBSD.org      
databases/vsqlite kwm@FreeBSD.org      
devel/autoconf-archive kwm@FreeBSD.org      
devel/gitg kwm@FreeBSD.org      
devel/libgdata kwm@FreeBSD.org      
devel/libgee kwm@FreeBSD.org      
devel/libgee06 kwm@FreeBSD.org      
devel/orc kwm@FreeBSD.org      
devel/regexxer kwm@FreeBSD.org      
games/monster-masher kwm@FreeBSD.org      
graphics/ImageMagick kwm@FreeBSD.org      
graphics/ImageMagick-nox11 kwm@FreeBSD.org      
graphics/ImageMagick7 kwm@FreeBSD.org      
graphics/ImageMagick7-nox11 kwm@FreeBSD.org      
graphics/argyllcms kwm@FreeBSD.org      
graphics/colord kwm@FreeBSD.org      
graphics/colord-gtk kwm@FreeBSD.org      
graphics/goocanvas kwm@FreeBSD.org      
graphics/goocanvas2 kwm@FreeBSD.org      
graphics/goocanvasmm2 kwm@FreeBSD.org      
graphics/py-goocanvas kwm@FreeBSD.org      
graphics/wayland-protocols kwm@FreeBSD.org      
java/netbeans kwm@FreeBSD.org      
java/netbeans-devel [I] kwm@FreeBSD.org      
lang/spidermonkey170 kwm@FreeBSD.org bad_C++_code
gcc4_error
   
lang/spidermonkey24 kwm@FreeBSD.org      
lang/spidermonkey38 kwm@FreeBSD.org      
mail/libmapi [B] kwm@FreeBSD.org      
misc/iso-codes kwm@FreeBSD.org      
misc/libisocodes kwm@FreeBSD.org      
multimedia/libde265 kwm@FreeBSD.org      
multimedia/pitivi kwm@FreeBSD.org      
net/gupnp-dlna kwm@FreeBSD.org      
net/libmms kwm@FreeBSD.org      
net/liferea kwm@FreeBSD.org      
science/chemical-mime-data kwm@FreeBSD.org      
science/gchemutils kwm@FreeBSD.org      
sysutils/accountsservice kwm@FreeBSD.org      
sysutils/zeitgeist kwm@FreeBSD.org      
textproc/highlight kwm@FreeBSD.org      
textproc/itstool kwm@FreeBSD.org      
www/gnome-web-photo kwm@FreeBSD.org      
www/libepc kwm@FreeBSD.org      
www/libsocialweb kwm@FreeBSD.org      
x11-toolkits/gtk-sharp30 kwm@FreeBSD.org      
x11-toolkits/libunique3 kwm@FreeBSD.org      
x11-toolkits/unique kwm@FreeBSD.org      
ports shown: 48   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.