Report created on Thu Sep 18 23:47:34 2014. back to main menu

NOTE: as of 20140601, GNATS has been deprecated. Until portsmon can catch up, expect the PR data to be stale.

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
databases/libdrizzle bdrewery@FreeBSD.org      
devel/ccache bdrewery@FreeBSD.org      
devel/cppunit bdrewery@FreeBSD.org      
devel/gearmand bdrewery@FreeBSD.org      
devel/gearmand-devel bdrewery@FreeBSD.org      
devel/privman bdrewery@FreeBSD.org      
devel/py-jellyfish bdrewery@FreeBSD.org      
devel/valgrind-devel bdrewery@FreeBSD.org      
devel/valgrind bdrewery@FreeBSD.org   152899: devel/valgrind: unhandled syscall: 506 bdrewery
185291: devel/valgrind segfaults with -d parametr bdrewery
irc/eggdrop bdrewery@FreeBSD.org      
irc/eggdrop-devel bdrewery@FreeBSD.org      
irc/ezbounce bdrewery@FreeBSD.org      
irc/rbot bdrewery@FreeBSD.org      
mail/dovecot bdrewery@FreeBSD.org   177497: mail/dovecot startup script breaks onestart functionality freebsd-ports-bu
mail/ezmlm bdrewery@FreeBSD.org      
mail/ezmlm-idx bdrewery@FreeBSD.org      
mail/mess822 bdrewery@FreeBSD.org      
mail/qmail bdrewery@FreeBSD.org      
mail/qmail-conf bdrewery@FreeBSD.org      
mail/qmail-contrib bdrewery@FreeBSD.org      
mail/qmail-dk bdrewery@FreeBSD.org      
mail/qmail-ldap bdrewery@FreeBSD.org      
mail/qmail-mysql bdrewery@FreeBSD.org      
mail/qmail-spamcontrol bdrewery@FreeBSD.org      
mail/qmail-tls bdrewery@FreeBSD.org      
mail/qmailadmin bdrewery@FreeBSD.org      
mail/qmailanalog bdrewery@FreeBSD.org      
mail/qmhandle bdrewery@FreeBSD.org      
mail/qtools bdrewery@FreeBSD.org      
mail/queue-fix bdrewery@FreeBSD.org      
mail/queue-repair bdrewery@FreeBSD.org      
mail/serialmail bdrewery@FreeBSD.org      
mail/spamdyke bdrewery@FreeBSD.org      
mail/vpopmail bdrewery@FreeBSD.org      
math/miracl bdrewery@FreeBSD.org compiler_error    
net-mgmt/bandwidthd bdrewery@FreeBSD.org      
net/6tunnel bdrewery@FreeBSD.org      
net/zebra bdrewery@FreeBSD.org      
ports-mgmt/portmaster bdrewery@FreeBSD.org   172651: ports-mgmt/portmaster --index and --index-only redundancy and processing error bdrewery
174729: ports-mgmt/portmaster: should check for script running as before doing certain operations bdrewery
180673: ports-mgmt/portmaster: shall not delete build deps that are run deps, too (e.g. math/cantor: fails on R stuff) bdrewery
181947: ports-mgmt/portmaster creates PKGDIR/ when WITH_PKGNG set bdrewery
189398: ports-mgmt/portmaster: portmaster -g does not always build intermediate ports bdrewery
ports-mgmt/portupgrade-devel bdrewery@FreeBSD.org   177365: [patch] ports-mgmt/portupgrade-devel enhancements bdrewery
ports-mgmt/portupgrade bdrewery@FreeBSD.org   127889: ports-mgmt/portupgrade detects spurious failures and skips ports unnecessarily bdrewery
184672: portupgrade -p libxcb fails to install x11/xcb-proto as dependency with staging bdrewery
185217: ports-mgmt/portupgrade: Building ports using a symbolic link in place of /usr/ports is broken bdrewery
185523: [PATCH] ports-mgmt/portupgrade: use ruby-bdb with ruby 2.0 again bdrewery
188084: ports-mgmt/portupgrade : not working without ruby-bdb bdrewery
190269: ports-mgmt/portupgrade with pkgng does not properly restart updated daemons bdrewery
ports-mgmt/poudriere-devel bdrewery@FreeBSD.org      
ports-mgmt/poudriere bdrewery@FreeBSD.org   180924: ports-mgmt/poudriere does not write changed port config bdrewery
181799: ports-mgmt/poudriere: [PATCH] allow in-line comments in ports-list bdrewery
security/gnutls bdrewery@FreeBSD.org      
security/keybase bdrewery@freebsd.org      
security/openssh-portable bdrewery@FreeBSD.org      
security/openssh-portable-base bdrewery@FreeBSD.org      
sysutils/beadm bdrewery@FreeBSD.org      
sysutils/beadm-devel bdrewery@FreeBSD.org      
sysutils/cronolog bdrewery@FreeBSD.org      
sysutils/cronolog-devel bdrewery@FreeBSD.org      
sysutils/daemontools bdrewery@FreeBSD.org      
sysutils/nfsping bdrewery@FreeBSD.org      
sysutils/zfstools bdrewery@FreeBSD.org      
textproc/jshon bdrewery@FreeBSD.org      
www/suphp bdrewery@FreeBSD.org      
ports shown: 56   ports with build errors: 1 ports with outstanding PRs: 6  
ports with either build errors or PRs: 7

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