Report created on Thu Jul 20 22:48:38 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/alsa-lib jbeich@FreeBSD.org      
audio/alsa-plugins jbeich@FreeBSD.org      
audio/alsa-utils jbeich@FreeBSD.org      
audio/wavbreaker jbeich@FreeBSD.org      
devel/android-tools-adb jbeich@FreeBSD.org      
devel/android-tools-adb-devel jbeich@FreeBSD.org      
devel/android-tools-fastboot jbeich@FreeBSD.org      
devel/android-tools-fastboot-devel jbeich@FreeBSD.org      
devel/android-tools-simpleperf jbeich@FreeBSD.org      
devel/fb-adb jbeich@FreeBSD.org      
devel/git-cinnabar jbeich@FreeBSD.org      
devel/googlemock jbeich@FreeBSD.org      
devel/googletest jbeich@FreeBSD.org      
devel/libopenbsd jbeich@FreeBSD.org      
devel/lua-luarocks jbeich@FreeBSD.org      
devel/onscripter jbeich@FreeBSD.org      
devel/onscripter-1byte jbeich@FreeBSD.org      
devel/ponscripter-sekai jbeich@FreeBSD.org      
devel/py-adb jbeich@FreeBSD.org      
devel/py-apscheduler jbeich@FreeBSD.org      
devel/py-atomiclong jbeich@FreeBSD.org      
devel/py-fusepy jbeich@FreeBSD.org      
devel/py-game_sdl2 jbeich@FreeBSD.org      
devel/py-libusb1 jbeich@FreeBSD.org      
devel/py-libusb115 jbeich@FreeBSD.org      
devel/py-pytest-asyncio jbeich@FreeBSD.org      
devel/py-pytest-tornado jbeich@FreeBSD.org      
devel/renpy jbeich@FreeBSD.org      
devel/renpy6 jbeich@FreeBSD.org      
devel/rlvm jbeich@FreeBSD.org      
dns/openmdns jbeich@FreeBSD.org      
emulators/citra jbeich@FreeBSD.org ???    
emulators/citra-qt5 jbeich@FreeBSD.org ???    
emulators/ppsspp jbeich@FreeBSD.org      
emulators/ppsspp-qt5 jbeich@FreeBSD.org      
emulators/rpcs3 jbeich@FreeBSD.org      
emulators/xsystem35 jbeich@FreeBSD.org      
games/aquaria jbeich@FreeBSD.org      
games/katawa-shoujo jbeich@FreeBSD.org      
games/narcissu2 jbeich@FreeBSD.org      
games/openbor jbeich@FreeBSD.org      
games/openbor3482 jbeich@FreeBSD.org      
games/openbor3711 jbeich@FreeBSD.org      
games/openbor3979 jbeich@FreeBSD.org      
games/openbor4432 jbeich@FreeBSD.org      
games/openra jbeich@FreeBSD.org      
graphics/colmap jbeich@FreeBSD.org      
graphics/sekrit-twc-zimg jbeich@FreeBSD.org      
graphics/vapoursynth-fmtconv jbeich@FreeBSD.org      
graphics/vapoursynth-waifu2x-w2xc jbeich@FreeBSD.org      
graphics/waifu2x-converter-cpp jbeich@FreeBSD.org      
mail/mpop jbeich@FreeBSD.org      
math/ceres-solver jbeich@FreeBSD.org linker_error    
multimedia/baka-mplayer jbeich@FreeBSD.org      
multimedia/ffms2 jbeich@FreeBSD.org      
multimedia/gnome-mpv jbeich@FreeBSD.org      
multimedia/kvazaar jbeich@FreeBSD.org      
multimedia/l-smash jbeich@FreeBSD.org      
multimedia/libmtp jbeich@FreeBSD.org linker_error    
multimedia/libvpx jbeich@FreeBSD.org      
multimedia/mpc-qt jbeich@FreeBSD.org      
multimedia/vapoursynth jbeich@FreeBSD.org      
multimedia/vapoursynth-l-smash-works jbeich@FreeBSD.org      
security/py-zxcvbn-python jbeich@FreeBSD.org      
sysutils/android-file-transfer jbeich@FreeBSD.org      
sysutils/android-file-transfer-qt4 jbeich@FreeBSD.org      
sysutils/android-file-transfer-qt5 jbeich@FreeBSD.org      
sysutils/fusefs-gitfs jbeich@FreeBSD.org      
sysutils/fusefs-simple-mtpfs jbeich@FreeBSD.org      
sysutils/rinse jbeich@FreeBSD.org      
sysutils/uhidd jbeich@FreeBSD.org      
textproc/py-colorclass jbeich@FreeBSD.org      
textproc/py-terminaltables jbeich@FreeBSD.org      
www/py-flexget jbeich@FreeBSD.org      
x11-drivers/xf86-input-wacom jbeich@FreeBSD.org      
x11/controllermap jbeich@FreeBSD.org      
ports shown: 76   ports with build errors: 4 ports with outstanding PRs: 0  
ports with either build errors or PRs: 4

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.