Report created on Wed May 24 10:25:10 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/libgpod-sharp mono@FreeBSD.org      
audio/taglib-sharp mono@FreeBSD.org      
deskutils/tomboy mono@FreeBSD.org      
deskutils/tomboy-plugin-latex mono@FreeBSD.org      
deskutils/tomboy-plugin-reminder mono@FreeBSD.org      
deskutils/tomboy-plugin-todo mono@FreeBSD.org      
devel/dbus-sharp mono@FreeBSD.org      
devel/dbus-sharp-glib mono@FreeBSD.org      
devel/gio-sharp mono@FreeBSD.org      
devel/mono-addins mono@FreeBSD.org      
devel/monodevelop mono@FreeBSD.org      
devel/ndesk-options mono@FreeBSD.org      
devel/notify-sharp mono@FreeBSD.org      
irc/smartirc4net mono@FreeBSD.org      
lang/fsharp mono@FreeBSD.org      
lang/mono mono@FreeBSD.org missing_header    
lang/mono-basic mono@FreeBSD.org      
lang/referenceassemblies-pcl mono@FreeBSD.org      
mail/gmime2-sharp mono@FreeBSD.org      
mail/gmime24-sharp mono@FreeBSD.org      
mail/gmime26-sharp mono@FreeBSD.org      
misc/podsleuth mono@FreeBSD.org      
multimedia/banshee [B] mono@FreeBSD.org      
net/avahi-sharp mono@FreeBSD.org      
net/mono-zeroconf mono@FreeBSD.org      
www/mod_mono mono@FreeBSD.org      
www/webkit-sharp mono@FreeBSD.org      
www/xsp mono@FreeBSD.org      
x11-toolkits/gnome-sharp20 mono@FreeBSD.org      
x11-toolkits/gtk-sharp-beans mono@FreeBSD.org      
x11-toolkits/gtk-sharp20 mono@FreeBSD.org      
x11-toolkits/libgdiplus mono@FreeBSD.org      
ports shown: 32   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.