Report created on Wed Aug 23 04:19:51 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/alure nemysis@FreeBSD.org      
devel/ruby-sdl nemysis@FreeBSD.org      
devel/sdlskk nemysis@FreeBSD.org      
games/3omns nemysis@FreeBSD.org      
games/asteroid nemysis@FreeBSD.org      
games/blobwars nemysis@FreeBSD.org      
games/bluemoon nemysis@FreeBSD.org      
games/bs nemysis@FreeBSD.org      
games/domination nemysis@FreeBSD.org      
games/galaxis nemysis@FreeBSD.org      
games/legend-of-edgar nemysis@FreeBSD.org      
games/lugaru nemysis@FreeBSD.org      
games/netwalk nemysis@FreeBSD.org      
games/opensurge nemysis@FreeBSD.org      
games/pacmanarena nemysis@FreeBSD.org      
games/pyspacewar nemysis@FreeBSD.org      
games/rnd_jue nemysis@FreeBSD.org      
games/rockdodger nemysis@FreeBSD.org      
games/rocksndiamonds nemysis@FreeBSD.org      
games/rocksndiamonds-data nemysis@FreeBSD.org      
games/sdl_scavenger nemysis@FreeBSD.org      
games/ski nemysis@FreeBSD.org      
games/starfighter nemysis@FreeBSD.org      
games/tong nemysis@FreeBSD.org      
games/traingame nemysis@FreeBSD.org      
games/twind nemysis@FreeBSD.org      
games/ultimatestunts nemysis@FreeBSD.org      
games/vms-empire nemysis@FreeBSD.org      
games/vodovod nemysis@FreeBSD.org      
games/wizznic nemysis@FreeBSD.org      
games/xgalaga++ nemysis@FreeBSD.org      
games/xgalaga-sdl nemysis@FreeBSD.org      
games/xye nemysis@FreeBSD.org      
graphics/viewnior nemysis@FreeBSD.org      
irc/py-fishcrypt nemysis@FreeBSD.org      
misc/gonvert nemysis@FreeBSD.org      
multimedia/smplayer nemysis@FreeBSD.org      
multimedia/smplayer-themes nemysis@FreeBSD.org      
net/enet nemysis@FreeBSD.org      
net/proxychains-ng nemysis@FreeBSD.org      
security/fpm2 nemysis@FreeBSD.org      
security/secpanel nemysis@FreeBSD.org      
x11-fonts/alfont [B] nemysis@FreeBSD.org      
x11/xautomation nemysis@FreeBSD.org      
ports shown: 44   ports with build errors: 0 ports with outstanding PRs: 0  
ports with either build errors or PRs: 0

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.