Report created on Sun Jul 23 20:53:39 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
audio/decibel-audio-player somicide@gmail.com manpage    
audio/mixxx ports@FreeBSD.org manpage    
audio/musescore ports@FreeBSD.org manpage    
biology/gmap bacon4000@gmail.com manpage    
biology/ugene h2+fbsdports@fsfe.org checksum
manpage
   
cad/meshlab ports@FreeBSD.org manpage    
chinese/ibus-chewing eric@camachat.org manpage    
chinese/sunpinyin lichray@gmail.com manpage    
databases/memcached swills@FreeBSD.org manpage    
databases/postgresql-plruby knu@FreeBSD.org manpage    
databases/soci jlaffaye@FreeBSD.org manpage    
databases/sqlitestudio yuri@rawbw.com manpage    
devel/cvs-devel bdheeman@gmail.com clang
manpage
   
devel/kore tobik@FreeBSD.org manpage    
devel/kore-notls tobik@FreeBSD.org manpage    
devel/libcfg rodrigo@FreeBSD.org manpage    
devel/libhtp koobs@FreeBSD.org manpage    
devel/liblas12 rhurlin@gwdg.de clang
manpage
   
devel/libxs vg@FreeBSD.org manpage    
devel/llvm-cheri brooks@FreeBSD.org manpage    
devel/llvm35 brooks@FreeBSD.org manpage    
devel/llvm38 brooks@FreeBSD.org manpage    
devel/pecl-qb gasol.wu@gmail.com manpage    
devel/pecl-swoole vanilla@FreeBSD.org manpage    
devel/php-uprofiler gasol.wu@gmail.com manpage    
devel/renpy jbeich@FreeBSD.org manpage    
dns/bundy mat@FreeBSD.org manpage    
graphics/cptutils amdmi3@FreeBSD.org manpage    
graphics/dspdfviewer santhosh.raju@gmail.com manpage    
graphics/gnofract4d ports@FreeBSD.org manpage    
graphics/mypaint ports@FreeBSD.org manpage    
graphics/photivo danfe@FreeBSD.org manpage    
graphics/pygts ports@FreeBSD.org manpage    
graphics/qcomicbook ports@FreeBSD.org manpage    
irc/ircd-ratbox-devel moggie@elasticmind.net manpage    
japanese/mecab ports@FreeBSD.org manpage    
java/sablevm java@FreeBSD.org manpage    
lang/erlang-runtime19 olgeni@FreeBSD.org compiler_error
linker_error
manpage
   
lang/erlang-runtime20 olgeni@FreeBSD.org compiler_error
linker_error
manpage
   
lang/gcc5-aux ports@FreeBSD.org manpage    
lang/gcc6-aux ports@FreeBSD.org manpage    
lang/gcc8-devel gerald@FreeBSD.org manpage    
lang/guile2 bofh@FreeBSD.org manpage    
lang/php70 tz@FreeBSD.org manpage    
lang/php71 tz@FreeBSD.org manpage    
lang/ruby23 ruby@FreeBSD.org manpage    
lang/ruby24 ruby@FreeBSD.org manpage    
lang/see numisemis@yahoo.com manpage    
lang/spidermonkey185 koobs@FreeBSD.org manpage    
mail/archiveopteryx feld@FreeBSD.org manpage    
mail/archiveopteryx-devel feld@FreeBSD.org manpage    
mail/cone ports@FreeBSD.org manpage    
mail/cyrus-imapd30 ume@FreeBSD.org manpage    
math/nlopt rhurlin@gwdg.de manpage    
math/py-matplotlib mainland@apeiron.net manpage    
multimedia/obs-studio ports@FreeBSD.org manpage    
net-im/ring-daemon yuri@rawbw.com ???
manpage
   
net-mgmt/ipv6calc dbaio@FreeBSD.org manpage    
net-p2p/dogecoin swills@FreeBSD.org checksum
manpage
   
net-p2p/retroshare peter@netkey.at manpage    
net/ipsumdump ports@FreeBSD.org manpage    
net/libzmq3 koobs@FreeBSD.org ???
manpage
   
net/ntp cy@FreeBSD.org manpage    
net/p5-Net-AMQP-RabbitMQ swills@FreeBSD.org manpage    
net/torsocks yuri@rawbw.com linker_error
manpage
   
print/scribus bsam@FreeBSD.org manpage    
science/clhep bofh@FreeBSD.org manpage    
science/paraview devel@stasyan.com manpage    
science/veusz devel@stasyan.com manpage    
security/nettle sunpoet@FreeBSD.org manpage    
security/openssl brnrd@FreeBSD.org manpage    
security/p5-Crypt-RHash perl@FreeBSD.org manpage    
security/p5-Digest-GOST pi@FreeBSD.org manpage    
security/pam_ssh_agent_auth ports@FreeBSD.org manpage    
security/quantis ale@FreeBSD.org manpage    
security/stunnel zi@FreeBSD.org manpage    
shells/bash-completion sunpoet@FreeBSD.org manpage    
sysutils/dateutils jessefrgsmith@yahoo.ca manpage    
sysutils/procenv ports@FreeBSD.org manpage    
sysutils/qzeitgeist avilla@FreeBSD.org manpage    
sysutils/sleuthkit antoine@FreeBSD.org manpage    
sysutils/tlsdate sunpoet@FreeBSD.org manpage    
textproc/randlm demon@FreeBSD.org manpage    
www/cherokee ports@FreeBSD.org manpage    
www/mod_jk girgen@FreeBSD.org manpage    
www/mod_php70 tz@FreeBSD.org manpage    
www/mod_php71 tz@FreeBSD.org manpage    
x11-wm/cde crees@FreeBSD.org linker_error
manpage
   
x11/leechcraft vg@FreeBSD.org manpage    
x11/mate-applets gnome@FreeBSD.org manpage    
ports shown: 90   ports with build errors: 90 ports with outstanding PRs: 0  
ports with either build errors or PRs: 90

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.