Report created on Tue Jun 27 12:09:24 2017. back to main menu


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/baudline [I] hamradio@FreeBSD.org      
audio/codec2 hamradio@FreeBSD.org      
comms/acfax hamradio@FreeBSD.org      
comms/aprsd hamradio@FreeBSD.org      
comms/chirp hamradio@FreeBSD.org      
comms/chu hamradio@FreeBSD.org      
comms/cqrlog hamradio@FreeBSD.org      
comms/cwdaemon hamradio@FreeBSD.org      
comms/ebook2cw hamradio@FreeBSD.org      
comms/ebook2cwgui hamradio@FreeBSD.org      
comms/echolinux hamradio@FreeBSD.org      
comms/fl_moxgen hamradio@FreeBSD.org      
comms/fldigi hamradio@FreeBSD.org      
comms/fllog hamradio@FreeBSD.org      
comms/flrig hamradio@FreeBSD.org      
comms/flwrap hamradio@FreeBSD.org      
comms/freedv hamradio@FreeBSD.org      
comms/ge-x2212 hamradio@FreeBSD.org      
comms/geoid hamradio@FreeBSD.org      
comms/gnuradio hamradio@FreeBSD.org      
comms/gpredict hamradio@FreeBSD.org      
comms/grig hamradio@FreeBSD.org      
comms/gtkmmorse hamradio@FreeBSD.org      
comms/hamlib hamradio@FreeBSD.org      
comms/hf hamradio@FreeBSD.org      
comms/ibp hamradio@FreeBSD.org      
comms/kb hamradio@FreeBSD.org      
comms/klog hamradio@FreeBSD.org      
comms/kvasd hamradio@FreeBSD.org      
comms/libfec hamradio@FreeBSD.org      
comms/linpsk hamradio@FreeBSD.org      
comms/linrad hamradio@FreeBSD.org      
comms/locator hamradio@FreeBSD.org      
comms/lysdr hamradio@FreeBSD.org      
comms/morse hamradio@FreeBSD.org      
comms/nasawash hamradio@FreeBSD.org      
comms/nec2c hamradio@FreeBSD.org      
comms/predict hamradio@FreeBSD.org      
comms/qrq hamradio@FreeBSD.org      
comms/qsstv hamradio@FreeBSD.org      
comms/qtel [B] hamradio@FreeBSD.org      
comms/quisk hamradio@FreeBSD.org      
comms/soundmodem hamradio@FreeBSD.org      
comms/splat hamradio@FreeBSD.org      
comms/svxlink [B] hamradio@FreeBSD.org      
comms/thebridge hamradio@FreeBSD.org      
comms/tlf hamradio@FreeBSD.org      
comms/trustedqsl hamradio@FreeBSD.org      
comms/unixcw hamradio@FreeBSD.org      
comms/usrp hamradio@FreeBSD.org      
comms/wsjt hamradio@FreeBSD.org      
comms/wsjtx hamradio@FreeBSD.org      
comms/wspr hamradio@FreeBSD.org      
comms/wwl hamradio@FreeBSD.org      
comms/xcwcp hamradio@FreeBSD.org      
comms/xnec2c hamradio@FreeBSD.org      
comms/xwota hamradio@FreeBSD.org      
comms/yaac hamradio@FreeBSD.org      
comms/yagiuda hamradio@FreeBSD.org      
comms/yfklog hamradio@FreeBSD.org      
irc/cwirc hamradio@FreeBSD.org      
science/gsmc hamradio@FreeBSD.org      
science/linsmith hamradio@FreeBSD.org      
science/simsmith hamradio@FreeBSD.org      
textproc/cwtext hamradio@FreeBSD.org      
ports shown: 65   ports with build errors: 0 ports with outstanding PRs: 0  
ports with either build errors or PRs: 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 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.