Report created on Mon Nov 24 20:12:29 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
astro/xplanet novel@FreeBSD.org  
audio/cymbaline novel@FreeBSD.org  
audio/easytag novel@FreeBSD.org  
audio/libcdaudio novel@FreeBSD.org  
audio/mp3blaster novel@FreeBSD.org  
audio/mpg123 novel@FreeBSD.org  
audio/p5-MP3-Tag novel@FreeBSD.org  
audio/scrobbler novel@FreeBSD.org  
audio/wmix novel@FreeBSD.org  
audio/xmms-scrobbler novel@FreeBSD.org  
benchmarks/dkftpbench novel@FreeBSD.org  
deskutils/hot-babe novel@FreeBSD.org  
deskutils/logjam novel@FreeBSD.org  
devel/libosinfo novel@FreeBSD.org  
devel/p5-Net-DBus novel@FreeBSD.org  
devel/phptags novel@FreeBSD.org  
devel/py-prettytable novel@FreeBSD.org  
lang/arena novel@FreeBSD.org  
mail/msmtp novel@FreeBSD.org  
misc/bdelta novel@FreeBSD.org  
misc/py-osd novel@FreeBSD.org  
net-mgmt/py-flowtools novel@FreeBSD.org  
net/py-libcloud novel@FreeBSD.org  
net/py-novaclient novel@FreeBSD.org  
net/py-pyzmq novel@FreeBSD.org  
net/wmnet novel@FreeBSD.org  
russian/artwiz-ru novel@FreeBSD.org  
security/libgpg-error novel@FreeBSD.org  
security/libtasn1 novel@FreeBSD.org  
security/opencdk novel@FreeBSD.org  
security/p11-kit novel@FreeBSD.org  
security/scanlogd novel@FreeBSD.org  
sysutils/cdf novel@FreeBSD.org  
sysutils/deltup novel@FreeBSD.org  
sysutils/gkrellfire novel@FreeBSD.org  
sysutils/pidof novel@FreeBSD.org  
sysutils/torsmo novel@FreeBSD.org  
x11-clocks/alltraxclock novel@FreeBSD.org  
x11-clocks/osdclock novel@FreeBSD.org  
x11-themes/openbox-themes novel@FreeBSD.org  
x11-wm/fbcmd novel@FreeBSD.org  
x11-wm/genmenu novel@FreeBSD.org  
x11-wm/obconf novel@FreeBSD.org  
x11-wm/openbox novel@FreeBSD.org  
x11/xidle novel@FreeBSD.org  
ports shown: 45 ports with build errors: 0

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.