Report created on Sun Apr 30 05:12:18 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/aucatctl tobik@FreeBSD.org      
audio/cmus tobik@FreeBSD.org      
audio/gstreamer1-plugins-sndio tobik@FreeBSD.org      
audio/pulseaudio-module-sndio tobik@FreeBSD.org      
audio/sndio tobik@FreeBSD.org      
audio/spectrogram tobik@FreeBSD.org      
databases/sqliteconvert tobik@FreeBSD.org      
devel/kore tobik@FreeBSD.org      
devel/ksql tobik@FreeBSD.org      
devel/leiningen tobik@FreeBSD.org      
devel/libconcurrent tobik@FreeBSD.org      
devel/linux-kernel tobik@FreeBSD.org      
devel/stack tobik@FreeBSD.org      
editors/mg tobik@FreeBSD.org      
games/ags tobik@FreeBSD.org      
games/iortcw tobik@FreeBSD.org      
games/openmw tobik@FreeBSD.org      
graphics/gcolor3 tobik@FreeBSD.org      
graphics/imv tobik@FreeBSD.org      
graphics/llpp tobik@FreeBSD.org      
graphics/netpbm tobik@FreeBSD.org      
java/intellij-fsnotifier tobik@FreeBSD.org      
java/intellij-pty4j tobik@FreeBSD.org      
java/jd-gui tobik@FreeBSD.org      
lang/chibi-scheme tobik@FreeBSD.org      
lang/myrddin tobik@FreeBSD.org      
multimedia/nordlicht tobik@FreeBSD.org      
net/ipxe tobik@FreeBSD.org      
net/sbm tobik@FreeBSD.org      
print/okc321 tobik@FreeBSD.org      
security/afl tobik@FreeBSD.org      
security/signify tobik@FreeBSD.org      
sysutils/acerhdf-kmod [I] tobik@FreeBSD.org      
sysutils/lr tobik@FreeBSD.org      
sysutils/showbeastie [I] tobik@FreeBSD.org      
sysutils/solaar tobik@FreeBSD.org      
sysutils/xe tobik@FreeBSD.org      
textproc/cmark tobik@FreeBSD.org      
www/stagit tobik@FreeBSD.org      
x11-fonts/terminus-ttf tobik@FreeBSD.org      
x11/simplestroke tobik@FreeBSD.org      
x11/workrave tobik@FreeBSD.org      
x11/xbanish tobik@FreeBSD.org      
ports shown: 43   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.