Report created on Tue Mar 28 20:09:36 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
archivers/peazip acm@FreeBSD.org      
audio/py-openal acm@FreeBSD.org      
devel/bullet acm@FreeBSD.org      
devel/ccrtp acm@FreeBSD.org linker_error    
devel/commoncpp acm@FreeBSD.org      
devel/dub acm@FreeBSD.org      
devel/libzrtpcpp acm@FreeBSD.org      
devel/ode acm@FreeBSD.org      
devel/p5-File-DesktopEntry acm@FreeBSD.org      
devel/p5-Gtk2-Spell acm@FreeBSD.org      
emulators/gngeo acm@FreeBSD.org clang-bug    
emulators/mednafen acm@FreeBSD.org configure_error
linker_error
   
emulators/mupen64plus acm@FreeBSD.org      
emulators/mupen64plus-audio-sdl acm@FreeBSD.org      
emulators/mupen64plus-core acm@FreeBSD.org      
emulators/mupen64plus-input-sdl acm@FreeBSD.org      
emulators/mupen64plus-plugins acm@FreeBSD.org      
emulators/mupen64plus-rsp-cxd4 acm@FreeBSD.org      
emulators/mupen64plus-rsp-hle acm@FreeBSD.org      
emulators/mupen64plus-rsp-z64 acm@FreeBSD.org      
emulators/mupen64plus-ui-console acm@FreeBSD.org      
emulators/mupen64plus-video-arachnoid acm@FreeBSD.org      
emulators/mupen64plus-video-glide64 acm@FreeBSD.org      
emulators/mupen64plus-video-glide64mk2 acm@FreeBSD.org      
emulators/mupen64plus-video-rice acm@FreeBSD.org      
emulators/mupen64plus-video-z64 acm@FreeBSD.org      
emulators/snes9x acm@FreeBSD.org      
emulators/stella acm@FreeBSD.org      
emulators/wxmupen64plus [B] acm@FreeBSD.org      
games/alienarena acm@FreeBSD.org linker_error    
games/alienarena-data acm@FreeBSD.org      
games/ceferino acm@FreeBSD.org      
games/chanta acm@FreeBSD.org      
games/el acm@FreeBSD.org      
games/el-data acm@FreeBSD.org      
games/fretsonfire acm@FreeBSD.org      
games/fretsonfire-data acm@FreeBSD.org      
games/naev acm@FreeBSD.org      
games/naev-data acm@FreeBSD.org      
games/sauerbraten acm@FreeBSD.org      
graphics/cal3d acm@FreeBSD.org      
graphics/guilib acm@FreeBSD.org      
graphics/libgltext acm@FreeBSD.org      
graphics/py-editobj acm@FreeBSD.org      
graphics/py-glewpy acm@FreeBSD.org      
lang/ldc acm@FreeBSD.org bad_C++_code    
mail/mbox2mdir acm@FreeBSD.org      
multimedia/smpeg acm@FreeBSD.org      
net-p2p/py-py2play acm@FreeBSD.org      
net-p2p/transmission-remote-gui acm@FreeBSD.org      
net/asio acm@FreeBSD.org      
net/py-tofu acm@FreeBSD.org      
science/checkmol acm@FreeBSD.org      
science/mol2ps acm@FreeBSD.org      
security/enchive acm@FreeBSD.org      
security/py-cerealizer acm@FreeBSD.org      
sysutils/bareos-bat acm@FreeBSD.org      
sysutils/bareos-client acm@FreeBSD.org runaway_process    
sysutils/bareos-client-static acm@FreeBSD.org runaway_process    
sysutils/bareos-docs acm@FreeBSD.org      
sysutils/bareos-server acm@FreeBSD.org      
sysutils/bareos-traymonitor acm@FreeBSD.org      
sysutils/hoz acm@FreeBSD.org      
www/bareos-webui acm@FreeBSD.org      
www/drupal8 acm@FreeBSD.org      
www/linux-opera acm@FreeBSD.org      
x11/alltray acm@FreeBSD.org      
x11/idesk acm@FreeBSD.org      
ports shown: 68   ports with build errors: 7 ports with outstanding PRs: 0  
ports with either build errors or PRs: 7

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.