Report created on Fri Dec 19 20:18:08 2014. back to main menu

NOTE: As of 20141128, PR imports from Bugzilla are in beta. Please contact linimon if you find any problems. Thanks.

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
audio/baresip crees@FreeBSD.org      
audio/id3ren crees@FreeBSD.org      
audio/musicpd crees@FreeBSD.org   155593: audio/musicpd .16.1 ignores embedded cue sheets in FLAC files with or without libcue installed crees@FreeBSD.org
195888: audio/musicpd build fails on ApeReplayGain.cxx [amd64] crees@FreeBSD.org
audio/qmidinet [B] crees@FreeBSD.org      
audio/re crees@FreeBSD.org      
audio/rebot3 crees@FreeBSD.org      
audio/rem crees@FreeBSD.org      
audio/soundtouch crees@FreeBSD.org      
audio/tkeca crees@FreeBSD.org      
comms/amtterm crees@FreeBSD.org      
databases/vfront crees@FreeBSD.org      
devel/cvs2html crees@FreeBSD.org      
devel/fmake crees@FreeBSD.org      
devel/libcfu crees@FreeBSD.org      
devel/maven-ant-tasks crees@FreeBSD.org      
devel/pybugz crees@FreeBSD.org      
devel/rclint crees@FreeBSD.org      
devel/ucpp crees@FreeBSD.org      
graphics/libprojectm crees@FreeBSD.org      
graphics/libvisual04 crees@FreeBSD.org      
graphics/projectm-libvisual crees@FreeBSD.org      
irc/charybdis crees@FreeBSD.org      
java/castor crees@FreeBSD.org      
java/jgraph crees@FreeBSD.org      
mail/automx crees@FreeBSD.org      
mail/biabam crees@FreeBSD.org      
mail/openwebmail crees@FreeBSD.org      
mail/qgmailnotifier crees@FreeBSD.org      
net-p2p/transmission-cli crees@FreeBSD.org   194029: net-p2p/transmission-cli: don't use bundled libraries crees@FreeBSD.org
net-p2p/transmission-daemon crees@FreeBSD.org      
net-p2p/transmission-gtk crees@FreeBSD.org   181095: net-p2p/transmission-gtk fails to start gnome@FreeBSD.org
net-p2p/transmission-qt4 crees@FreeBSD.org   183464: net-p2p/transmission-qt4: crash transmission-qt4 after start crees@FreeBSD.org
net-p2p/transmission crees@FreeBSD.org   186978: net-p2p/transmission depends on base openssl WITH_OPENSSL_PORT crees@FreeBSD.org
net/get_iplayer crees@FreeBSD.org      
net/openradius crees@FreeBSD.org      
net/opentracker crees@FreeBSD.org      
net/ssltunnel-client crees@FreeBSD.org      
net/ssltunnel-server crees@FreeBSD.org      
ports-mgmt/portdowngrade crees@FreeBSD.org      
ports-mgmt/tinderbox crees@FreeBSD.org      
ports-mgmt/tinderbox-devel crees@FreeBSD.org      
security/cfs crees@FreeBSD.org      
security/gorilla crees@FreeBSD.org      
sysutils/aird crees@FreeBSD.org      
sysutils/keyboard-daemon crees@FreeBSD.org      
sysutils/monitorix crees@FreeBSD.org      
sysutils/reed crees@FreeBSD.org      
sysutils/runit crees@FreeBSD.org      
textproc/atom crees@FreeBSD.org      
www/htdigest crees@FreeBSD.org      
www/mnogosearch crees@FreeBSD.org      
www/p5-CGI-Enurl crees@FreeBSD.org      
www/transmission-web crees@FreeBSD.org      
x11-toolkits/skinlf crees@FreeBSD.org      
ports shown: 54   ports with build errors: 0 ports with outstanding PRs: 5  
ports with either build errors or PRs: 5

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.