Report created on Thu Aug 24 03:00:31 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
archivers/gzip johans@FreeBSD.org      
comms/minicom johans@FreeBSD.org      
converters/mmencode johans@FreeBSD.org      
databases/gdbm johans@FreeBSD.org      
deskutils/gcal johans@FreeBSD.org      
deskutils/ljclive johans@FreeBSD.org      
devel/cppi johans@FreeBSD.org      
devel/cscope johans@FreeBSD.org      
devel/gindent johans@FreeBSD.org      
devel/opencvs johans@FreeBSD.org      
devel/patch johans@FreeBSD.org      
dns/dnsutl johans@FreeBSD.org      
dns/walker johans@FreeBSD.org      
editors/manedit johans@FreeBSD.org      
editors/nvi-devel johans@FreeBSD.org      
emulators/catapult johans@FreeBSD.org      
emulators/openmsx johans@FreeBSD.org      
games/KnightCap johans@FreeBSD.org      
games/crafty johans@FreeBSD.org ???
bad_C++_code
new_compiler_error
   
games/eboard johans@FreeBSD.org      
games/eif johans@FreeBSD.org      
games/freeciv johans@FreeBSD.org      
games/freeciv-nox11 johans@FreeBSD.org      
games/gnuchess johans@FreeBSD.org runaway_process    
games/gnushogi johans@FreeBSD.org      
games/hoichess johans@FreeBSD.org      
games/kcheckers johans@FreeBSD.org      
games/ldmud johans@FreeBSD.org      
games/ltris johans@FreeBSD.org      
games/mahjong johans@FreeBSD.org      
games/phalanx johans@FreeBSD.org      
games/ptkei johans@FreeBSD.org      
games/tetrinet johans@FreeBSD.org      
games/wolfpack johans@FreeBSD.org      
games/xboard johans@FreeBSD.org      
games/xcheckers johans@FreeBSD.org      
games/xshogi johans@FreeBSD.org      
graphics/xpaint johans@FreeBSD.org      
irc/irc johans@FreeBSD.org      
lang/afnix johans@FreeBSD.org ???    
lang/algol68g johans@FreeBSD.org      
lang/gawk johans@FreeBSD.org      
lang/gforth johans@FreeBSD.org      
lang/gnu-cobol johans@FreeBSD.org      
lang/intercal johans@FreeBSD.org      
lang/mawk johans@FreeBSD.org      
lang/mosml johans@FreeBSD.org arch    
lang/oo2c johans@FreeBSD.org      
lang/pfe johans@FreeBSD.org      
lang/smalltalk johans@FreeBSD.org      
lang/snobol4 johans@FreeBSD.org      
lang/swi-pl johans@FreeBSD.org      
lang/yorick johans@FreeBSD.org      
mail/archmbox johans@FreeBSD.org      
mail/chk4mail johans@FreeBSD.org      
mail/emil johans@FreeBSD.org      
math/calc johans@FreeBSD.org      
math/sc johans@FreeBSD.org      
misc/gwhich johans@FreeBSD.org      
misc/patchutils johans@FreeBSD.org      
net-im/climm johans@FreeBSD.org      
net/arp-scan johans@FreeBSD.org configure_error    
net/tinyfugue johans@FreeBSD.org      
news/cleanfeed johans@FreeBSD.org      
news/inn johans@FreeBSD.org      
news/nn johans@FreeBSD.org      
news/slrn johans@FreeBSD.org      
news/tin johans@FreeBSD.org      
news/trn johans@FreeBSD.org      
news/trn4 johans@FreeBSD.org      
news/xrn johans@FreeBSD.org      
print/enscript-a4 johans@FreeBSD.org      
print/enscript-letter johans@FreeBSD.org      
print/enscript-letterdj johans@FreeBSD.org      
print/paps johans@FreeBSD.org      
security/gsasl johans@FreeBSD.org      
security/gss johans@FreeBSD.org      
security/libssh johans@FreeBSD.org ???    
security/netpgp johans@FreeBSD.org      
security/nikto johans@FreeBSD.org      
security/osslsigncode johans@FreeBSD.org      
security/pgpdump johans@FreeBSD.org      
security/pidentd johans@FreeBSD.org      
security/shishi johans@FreeBSD.org      
security/signing-party johans@FreeBSD.org      
security/sks johans@FreeBSD.org      
security/ssss johans@FreeBSD.org      
security/tlswrap johans@FreeBSD.org      
security/wolfssl johans@FreeBSD.org      
shells/osh johans@FreeBSD.org      
sysutils/linrename johans@FreeBSD.org      
sysutils/mcron johans@FreeBSD.org      
sysutils/rdate johans@FreeBSD.org      
textproc/bibtool johans@FreeBSD.org      
textproc/diffutils johans@FreeBSD.org      
textproc/flex johans@FreeBSD.org      
textproc/gnugrep johans@FreeBSD.org      
textproc/gsed johans@FreeBSD.org      
textproc/texi2html johans@FreeBSD.org      
textproc/xml-format johans@FreeBSD.org      
www/caudium14 johans@FreeBSD.org      
www/lynx-current johans@FreeBSD.org      
www/qdecoder johans@FreeBSD.org      
www/xshttpd johans@FreeBSD.org linker_error    
www/xshttpd-devel johans@FreeBSD.org linker_error    
x11/xclip johans@FreeBSD.org      
x11/xsnow johans@FreeBSD.org      
ports shown: 107   ports with build errors: 8 ports with outstanding PRs: 0  
ports with either build errors or PRs: 8

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.