Report created on Sun Aug 20 05:53:01 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
benchmarks/scimark2 thierry@FreeBSD.org      
benchmarks/scimark2c thierry@FreeBSD.org      
cad/astk-client thierry@FreeBSD.org      
cad/astk-serveur thierry@FreeBSD.org      
cad/kicad thierry@FreeBSD.org linker_error    
cad/kicad-library thierry@FreeBSD.org      
cad/opencascade thierry@FreeBSD.org      
cad/scotch thierry@FreeBSD.org      
converters/ascii2binary thierry@FreeBSD.org      
deskutils/pinot thierry@FreeBSD.org ???    
devel/bouml-doc thierry@FreeBSD.org      
devel/libuv thierry@FreeBSD.org      
devel/netscape-java40 thierry@FreeBSD.org      
editors/mined thierry@FreeBSD.org      
finance/grisbi thierry@FreeBSD.org      
french/aster thierry@FreeBSD.org      
french/eficas thierry@FreeBSD.org      
french/homard thierry@FreeBSD.org      
french/med thierry@FreeBSD.org      
games/cardpics thierry@FreeBSD.org      
games/libmaitretarot thierry@FreeBSD.org      
games/libmt_client thierry@FreeBSD.org      
games/maitretarot thierry@FreeBSD.org      
games/monsterz thierry@FreeBSD.org      
games/mt_dolphin_ia thierry@FreeBSD.org      
games/mt_gtk_client thierry@FreeBSD.org      
games/pinball thierry@FreeBSD.org      
graphics/SciPlot thierry@FreeBSD.org      
graphics/cimg thierry@FreeBSD.org      
graphics/cosmoplayer thierry@FreeBSD.org      
graphics/libboard thierry@FreeBSD.org new_compiler_error    
graphics/xd3d thierry@FreeBSD.org      
mail/panda-cclient thierry@FreeBSD.org      
mail/panda-imap thierry@FreeBSD.org      
mail/spambnc thierry@FreeBSD.org      
math/mathmod thierry@FreeBSD.org      
math/metis-edf thierry@FreeBSD.org      
math/rkward-kde4 thierry@FreeBSD.org      
multimedia/winff thierry@FreeBSD.org      
net-im/tox thierry@FreeBSD.org      
net-im/toxic thierry@FreeBSD.org      
net-p2p/twister thierry@FreeBSD.org      
net/mpich2 thierry@FreeBSD.org configure_error    
net/neubot thierry@FreeBSD.org      
news/newsx thierry@FreeBSD.org      
print/fpdf thierry@FreeBSD.org      
science/bft thierry@FreeBSD.org      
science/cgnslib thierry@FreeBSD.org      
science/ecs thierry@FreeBSD.org      
science/fvm thierry@FreeBSD.org      
science/gnudatalanguage thierry@FreeBSD.org      
science/hdf5-18 thierry@FreeBSD.org      
science/medit thierry@FreeBSD.org      
science/mei thierry@FreeBSD.org      
science/ncs thierry@FreeBSD.org      
science/v_sim thierry@FreeBSD.org      
sysutils/uniutils thierry@FreeBSD.org      
sysutils/xvidcap thierry@FreeBSD.org      
textproc/CLDR thierry@FreeBSD.org      
textproc/R-cran-R2HTML thierry@FreeBSD.org      
textproc/UCD thierry@FreeBSD.org      
textproc/ibus-typing-booster thierry@FreeBSD.org      
textproc/jarnal thierry@FreeBSD.org      
textproc/libtextcat thierry@FreeBSD.org      
textproc/py-enchant thierry@FreeBSD.org      
textproc/py-hunspell thierry@FreeBSD.org      
textproc/py3-hunspell thierry@FreeBSD.org      
textproc/spellutils thierry@FreeBSD.org      
www/tidy-devel thierry@FreeBSD.org      
www/tidy-html5 thierry@FreeBSD.org      
www/tidy-lib thierry@FreeBSD.org      
www/tt-rss thierry@FreeBSD.org      
www/xpi-uBlock_origin thierry@FreeBSD.org      
x11-fonts/code2000 thierry@FreeBSD.org      
x11-fonts/liberation-fonts-ttf thierry@FreeBSD.org      
x11-fonts/stix-fonts thierry@FreeBSD.org      
x11/rxvt-unicode thierry@FreeBSD.org      
ports shown: 77   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.