Report created on Wed Mar 29 20:53:17 2017. back to main menu


Enter a new build error (partial match is ok) to get information about FreeBSD ports with that error:

Build error: 

For explanatory information and summary details, see the notes below.

portname maintainer build error logs Problem Reports Responsible
archivers/arj garga@FreeBSD.org coredump    
audio/kid3-qt4 jhale@FreeBSD.org ???
coredump
   
audio/qmpdclient uyamba@gmail.com coredump    
biology/plinkseq bacon4000@gmail.com bad_C++_code
coredump
   
databases/akonadi kde@FreeBSD.org coredump    
databases/sqlitebrowser lbartoletti@tuxfamily.org ???
coredump
   
devel/godot FreeBSD@Shaneware.biz coredump    
devel/godot-tools FreeBSD@Shaneware.biz coredump    
devel/ice freebsd@grem.de ???
coredump
   
devel/msp430-debug-stack lev@FreeBSD.org coredump    
devel/rubygem-glib2 ruby@FreeBSD.org coredump    
devel/shiboken wg@FreeBSD.org coredump    
emulators/aqemu ports@FreeBSD.org ???
coredump
   
emulators/ppsspp-qt4 jbeich@FreeBSD.org coredump    
emulators/qtemu ports@FreeBSD.org coredump    
games/chessx ports@freebsd.org coredump    
games/gnuchess johans@FreeBSD.org coredump    
games/hyperrogue amdmi3@FreeBSD.org ???
coredump
   
games/openglad ports@FreeBSD.org coredump    
games/tbe ports@FreeBSD.org coredump    
graphics/OpenEXR mandree@FreeBSD.org ???
coredump
   
graphics/djview4-qt4 ports@FreeBSD.org coredump    
graphics/gnofract4d ports@FreeBSD.org coredump    
graphics/qcomicbook ports@FreeBSD.org ???
coredump
   
irc/undernet-ircu freebsd-ports@dan.me.uk coredump
runaway_process
   
lang/dmd2 cy@FreeBSD.org coredump
linker_error
new_compiler_error
   
lang/hugs haskell@FreeBSD.org coredump    
lang/libjit (unknown) clang
coredump
   
lang/scm mi@aldan.algebra.com ???
coredump
missing_header
process_failed
   
mail/cone ports@FreeBSD.org coredump
runaway_process
   
math/PDL perl@FreeBSD.org coredump    
misc/freebsd-doc-el doceng@FreeBSD.org coredump    
misc/freebsd-doc-en doceng@FreeBSD.org coredump    
misc/freebsd-doc-hu doceng@FreeBSD.org coredump    
misc/freebsd-doc-it doceng@FreeBSD.org coredump    
misc/freebsd-doc-mn doceng@FreeBSD.org coredump    
misc/freebsd-doc-nl doceng@FreeBSD.org coredump    
misc/freebsd-doc-pl doceng@FreeBSD.org coredump    
misc/freebsd-doc-ru doceng@FreeBSD.org coredump    
misc/freebsd-doc-zh_cn doceng@FreeBSD.org coredump    
multimedia/dvbcut se@FreeBSD.org coredump    
multimedia/kvazaar jbeich@FreeBSD.org coredump    
multimedia/umplayer lichray@gmail.com coredump    
net-im/licq-qt-gui dinoex@FreeBSD.org ???
coredump
   
net-p2p/bitcoin robbak@robbak.com coredump    
net-p2p/eiskaltdcpp-qt fjoe@FreeBSD.org ???
coredump
   
net-p2p/litecoin swills@FreeBSD.org coredump    
net-p2p/valknut ports@FreeBSD.org coredump    
net/cagibi kde@FreeBSD.org ???
coredump
   
net/x2goclient ports@FreeBSD.org coredump    
news/nntpcache ports@FreeBSD.org coredump    
print/qpdfview vg@FreeBSD.org coredump    
science/libint ports@FreeBSD.org coredump    
security/clambc zi@FreeBSD.org configure_error
coredump
   
security/keepassx2 eric@camachat.org ???
coredump
   
security/qtkeychain-qt4 6yearold@gmail.com coredump    
sysutils/policykit-qt kde@FreeBSD.org coredump    
sysutils/qpxtool ports@FreeBSD.org coredump    
www/anyterm douglas@douglasthrift.net coredump
linker_error
   
x11-fonts/fontmatrix ports@FreeBSD.org coredump    
x11-wm/e-module-alarm enlightenment@FreeBSD.org coredump    
x11/qxkb ports@FreeBSD.org ???
coredump
   
x11/xgrab ports@FreeBSD.org coredump
runaway_process
   
ports shown: 63   ports with build errors: 63 ports with outstanding PRs: 0  
ports with either build errors or PRs: 63

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.