Report created on Wed Aug 23 19:22:23 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/cueplayer vg@FreeBSD.org      
audio/deadbeef vg@FreeBSD.org      
audio/gvolwheel vg@FreeBSD.org      
audio/lastfm-desktop vg@FreeBSD.org ???
manpage
   
audio/minitunes vg@FreeBSD.org      
audio/rubygem-librmpd vg@FreeBSD.org      
benchmarks/nosqlbench vg@FreeBSD.org clang    
cad/qelectrotech vg@FreeBSD.org      
converters/fondu vg@FreeBSD.org      
converters/ocaml-base64 vg@FreeBSD.org      
converters/ocaml-jsonm vg@FreeBSD.org      
databases/p5-DR-Tarantool vg@FreeBSD.org      
databases/p5-MR-Tarantool vg@FreeBSD.org      
databases/php5-tarantool vg@FreeBSD.org      
databases/py-tarantool vg@FreeBSD.org      
databases/rubygem-tarantool vg@FreeBSD.org      
databases/tarantool vg@FreeBSD.org      
databases/tarantool-c vg@FreeBSD.org      
deskutils/conkyemail vg@FreeBSD.org      
deskutils/conkyforecast vg@FreeBSD.org      
deskutils/plasma-applet-fancytasks vg@FreeBSD.org      
deskutils/plasma-applet-simpleweatherforecast vg@FreeBSD.org      
deskutils/znotes vg@FreeBSD.org      
devel/avro vg@FreeBSD.org      
devel/avro-c vg@FreeBSD.org      
devel/avro-cpp vg@FreeBSD.org      
devel/busybee vg@FreeBSD.org      
devel/cityhash vg@FreeBSD.org      
devel/libe vg@FreeBSD.org      
devel/libpo6 vg@FreeBSD.org      
devel/libxs vg@FreeBSD.org ???    
devel/lockfree-malloc vg@FreeBSD.org      
devel/msgpuck vg@FreeBSD.org      
devel/ocaml-re vg@FreeBSD.org      
devel/ocaml-uutf vg@FreeBSD.org      
devel/py-avro vg@FreeBSD.org      
devel/py-palm vg@FreeBSD.org      
devel/py-tarantool-queue vg@FreeBSD.org      
devel/qross vg@FreeBSD.org      
devel/rubygem-bin_utils vg@FreeBSD.org      
devel/rubygem-murmurhash3 vg@FreeBSD.org      
devel/rubygem-sumbur vg@FreeBSD.org      
devel/smack vg@FreeBSD.org      
emulators/gem5 vg@FreeBSD.org ???    
graphics/easypaint vg@FreeBSD.org      
graphics/impressive vg@FreeBSD.org      
graphics/scantailor vg@FreeBSD.org      
graphics/zint vg@FreeBSD.org      
lang/angelscript vg@FreeBSD.org      
misc/qmetro vg@FreeBSD.org      
multimedia/clipgrab vg@FreeBSD.org      
multimedia/mediadownloader vg@FreeBSD.org      
multimedia/qt4-mobility vg@FreeBSD.org      
net-im/py-jabberbot vg@FreeBSD.org      
net-im/py-xmpppy vg@FreeBSD.org      
net-im/qxmpp vg@FreeBSD.org      
net-im/qxmpp-qt5 vg@FreeBSD.org      
net-im/vacuum-im vg@FreeBSD.org      
net-mgmt/glpi-plugins-fusioninventory-server vg@FreeBSD.org      
net-mgmt/p5-FusionInventory-Agent vg@FreeBSD.org      
net-mgmt/qkismet vg@FreeBSD.org      
net-mgmt/sx vg@FreeBSD.org ???    
net/openpgm vg@FreeBSD.org      
net/rubygem-iproto vg@FreeBSD.org      
net/toonel vg@FreeBSD.org      
print/p5-Net-CUPS vg@FreeBSD.org      
print/qpdfview vg@FreeBSD.org      
russian/stardict-computer vg@FreeBSD.org      
russian/stardict-engcom vg@FreeBSD.org      
russian/stardict-pc vg@FreeBSD.org      
science/massxpert vg@FreeBSD.org      
science/qtresistors vg@FreeBSD.org      
security/ckpass vg@FreeBSD.org      
security/kqoauth vg@FreeBSD.org      
security/libkpass vg@FreeBSD.org      
security/retranslator vg@FreeBSD.org      
sysutils/cpuburn avg@FreeBSD.org      
sysutils/dmg2img vg@FreeBSD.org      
sysutils/hfsexplorer vg@FreeBSD.org      
sysutils/i2c-tools avg@FreeBSD.org      
textproc/confetti vg@FreeBSD.org      
textproc/ctpp2 vg@FreeBSD.org      
textproc/libflate vg@FreeBSD.org      
textproc/py-pyctpp2 vg@FreeBSD.org      
www/blastbeat vg@FreeBSD.org fetch    
www/mongrel2 vg@FreeBSD.org      
www/p5-Catalyst-Model-Tarantool vg@FreeBSD.org      
www/py-http-parser vg@FreeBSD.org      
www/sxweb vg@FreeBSD.org      
x11-fonts/font-gost vg@FreeBSD.org      
x11-fonts/pingwi vg@FreeBSD.org      
x11-themes/cursor-chameleon-anthracite vg@FreeBSD.org      
x11-themes/cursor-chameleon-darkskyblue vg@FreeBSD.org      
x11-themes/cursor-chameleon-pearl vg@FreeBSD.org      
x11-themes/cursor-chameleon-skyblue vg@FreeBSD.org      
x11-themes/cursor-chameleon-white vg@FreeBSD.org      
x11-themes/cursor-ecliz vg@FreeBSD.org      
x11-themes/kde4-windeco-crystal vg@FreeBSD.org      
x11-themes/kde4-windeco-dekorator vg@FreeBSD.org      
x11/leechcraft vg@FreeBSD.org ???    
x11/xwinwrap vg@FreeBSD.org      
ports shown: 101   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.