Report created on Thu Jul 31 23:45:03 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
archivers/arc delphij@FreeBSD.org      
archivers/lrzip delphij@FreeBSD.org      
archivers/lzlib delphij@FreeBSD.org      
archivers/pigz delphij@FreeBSD.org      
archivers/plzip delphij@FreeBSD.org      
chinese/docproj delphij@FreeBSD.org      
comms/zmtx-zmrx delphij@FreeBSD.org      
databases/lmdb delphij@FreeBSD.org      
databases/pecl-memcached delphij@FreeBSD.org   182449: databases/pecl-memcached: Memcached::setSaslAuthData unavailable, by lack of SASL authentication option, freebsd-ports-bu
187657: [PATCH] Remove non-relevant dependencies for databases/pecl-memcached miwi
devel/hgsvn delphij@FreeBSD.org      
devel/isl delphij@FreeBSD.org      
devel/jsl delphij@FreeBSD.org      
devel/libburn delphij@FreeBSD.org      
devel/libinotify delphij@FreeBSD.org      
devel/libisofs delphij@FreeBSD.org      
devel/py-ujson delphij@FreeBSD.org      
mail/libvmime delphij@FreeBSD.org      
mail/missey delphij@FreeBSD.org      
net/iet [I] delphij@FreeBSD.org fetch    
net/openldap24-client delphij@FreeBSD.org      
net/openldap24-sasl-client delphij@FreeBSD.org      
net/openldap24-server delphij@FreeBSD.org   132576: net/openldap24-server: multipying LDAP trees on the single server is impossible delphij
184053: net/openldap24-server: perl_back.h:22:18: error: perl.h: No such file or directory delphij
security/cryptopp delphij@FreeBSD.org      
sysutils/ddpt delphij@FreeBSD.org      
sysutils/sdparm delphij@FreeBSD.org      
sysutils/sg3_utils delphij@FreeBSD.org      
sysutils/smp_utils delphij@FreeBSD.org      
sysutils/xorriso delphij@FreeBSD.org      
textproc/fixrtf delphij@FreeBSD.org      
www/dokuwiki delphij@FreeBSD.org      
ports shown: 30   ports with build errors: 1 ports with outstanding PRs: 2  
ports with either build errors or PRs: 3

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.