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 manpage    
audio/mixxx manpage    
audio/musescore manpage    
biology/gmap manpage    
biology/ugene checksum
cad/meshlab manpage    
chinese/ibus-chewing manpage    
chinese/sunpinyin manpage    
databases/memcached manpage    
databases/postgresql-plruby manpage    
databases/soci manpage    
databases/sqlitestudio manpage    
devel/cvs-devel clang
devel/kore manpage    
devel/kore-notls manpage    
devel/libcfg manpage    
devel/libhtp manpage    
devel/liblas12 clang
devel/libxs manpage    
devel/llvm-cheri manpage    
devel/llvm35 manpage    
devel/llvm38 manpage    
devel/pecl-qb manpage    
devel/pecl-swoole manpage    
devel/php-uprofiler manpage    
devel/renpy manpage    
dns/bundy manpage    
graphics/cptutils manpage    
graphics/dspdfviewer manpage    
graphics/gnofract4d manpage    
graphics/mypaint manpage    
graphics/photivo manpage    
graphics/pygts manpage    
graphics/qcomicbook manpage    
irc/ircd-ratbox-devel manpage    
japanese/mecab manpage    
java/sablevm manpage    
lang/erlang-runtime19 compiler_error
lang/erlang-runtime20 compiler_error
lang/gcc5-aux manpage    
lang/gcc6-aux manpage    
lang/gcc8-devel manpage    
lang/guile2 manpage    
lang/php70 manpage    
lang/php71 manpage    
lang/ruby23 manpage    
lang/ruby24 manpage    
lang/see manpage    
lang/spidermonkey185 manpage    
mail/archiveopteryx manpage    
mail/archiveopteryx-devel manpage    
mail/cone manpage    
mail/cyrus-imapd30 manpage    
math/nlopt manpage    
math/py-matplotlib manpage    
multimedia/obs-studio manpage    
net-im/ring-daemon ???
net-mgmt/ipv6calc manpage    
net-p2p/dogecoin checksum
net-p2p/retroshare manpage    
net/ipsumdump manpage    
net/libzmq3 ???
net/ntp manpage    
net/p5-Net-AMQP-RabbitMQ manpage    
net/torsocks linker_error
print/scribus manpage    
science/clhep manpage    
science/paraview manpage    
science/veusz manpage    
security/nettle manpage    
security/openssl manpage    
security/p5-Crypt-RHash manpage    
security/p5-Digest-GOST manpage    
security/pam_ssh_agent_auth manpage    
security/quantis manpage    
security/stunnel manpage    
shells/bash-completion manpage    
sysutils/dateutils manpage    
sysutils/procenv manpage    
sysutils/qzeitgeist manpage    
sysutils/sleuthkit manpage    
sysutils/tlsdate manpage    
textproc/randlm manpage    
www/cherokee manpage    
www/mod_jk manpage    
www/mod_php70 manpage    
www/mod_php71 manpage    
x11-wm/cde linker_error
x11/leechcraft manpage    
x11/mate-applets manpage    
ports shown: 90   ports with build errors: 90 ports with outstanding PRs: 0  
ports with either build errors or PRs: 90


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 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.