Report created on Thu Aug 24 03:08:22 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
archivers/libunrar5 jhale@FreeBSD.org      
audio/acoustid-fingerprinter jhale@FreeBSD.org      
audio/aubio jhale@FreeBSD.org      
audio/audex jhale@FreeBSD.org      
audio/chromaprint jhale@FreeBSD.org      
audio/gogglesmm jhale@FreeBSD.org      
audio/kid3-kde4 jhale@FreeBSD.org      
audio/kid3-qt4 jhale@FreeBSD.org      
audio/kid3-qt5 jhale@FreeBSD.org      
audio/libcoverart jhale@FreeBSD.org      
audio/libdiscid jhale@FreeBSD.org      
audio/liblastfm jhale@FreeBSD.org      
audio/libmusicbrainz3 jhale@FreeBSD.org      
audio/libmusicbrainz5 jhale@FreeBSD.org      
audio/picard jhale@FreeBSD.org      
audio/py-aubio jhale@FreeBSD.org      
audio/py-discid jhale@FreeBSD.org      
audio/py-musicbrainz2 jhale@FreeBSD.org      
audio/taglib jhale@FreeBSD.org      
audio/xmmsctrl jhale@FreeBSD.org      
cad/librecad jhale@FreeBSD.org      
deskutils/plasma-applet-daisy jhale@FreeBSD.org      
deskutils/plasma-applet-panelspacer jhale@FreeBSD.org      
deskutils/plasma-applet-serverstatuswidget jhale@FreeBSD.org      
deskutils/plasma-applet-teacooker jhale@FreeBSD.org      
deskutils/plasma-applet-yawp jhale@FreeBSD.org      
devel/gwenhywfar jhale@FreeBSD.org      
devel/gwenhywfar-fox16 jhale@FreeBSD.org      
devel/gwenhywfar-gtk2 jhale@FreeBSD.org      
devel/gwenhywfar-qt4 jhale@FreeBSD.org      
devel/gwenhywfar-qt5 jhale@FreeBSD.org      
devel/libchipcard jhale@FreeBSD.org      
devel/npth jhale@FreeBSD.org      
finance/aqbanking jhale@FreeBSD.org      
finance/kmymoney-kde4 jhale@FreeBSD.org      
finance/ktoblzcheck jhale@FreeBSD.org      
finance/libalkimia jhale@FreeBSD.org      
finance/libofx jhale@FreeBSD.org      
graphics/frei0r jhale@FreeBSD.org      
graphics/frei0r-plugins jhale@FreeBSD.org      
graphics/frei0r-plugins-gavl jhale@FreeBSD.org      
graphics/frei0r-plugins-opencv jhale@FreeBSD.org      
graphics/libopenraw jhale@FreeBSD.org      
graphics/libpgf jhale@FreeBSD.org      
graphics/libraw jhale@FreeBSD.org      
mail/anubis jhale@FreeBSD.org      
math/convertall jhale@FreeBSD.org      
math/fftw3 jhale@FreeBSD.org      
math/fftw3-float jhale@FreeBSD.org      
math/fftw3-long jhale@FreeBSD.org      
math/fftw3-quad jhale@FreeBSD.org      
math/libqalculate jhale@FreeBSD.org      
math/qalculate jhale@FreeBSD.org      
math/rpcalc jhale@FreeBSD.org      
misc/krecipes-kde4 jhale@FreeBSD.org      
misc/nut jhale@FreeBSD.org      
multimedia/kmplayer-kde4 jhale@FreeBSD.org      
net-p2p/phex jhale@FreeBSD.org      
print/latexdiff jhale@FreeBSD.org      
security/cryptopp jhale@FreeBSD.org      
security/gpa jhale@FreeBSD.org      
security/gpgme jhale@FreeBSD.org      
security/gpgme-cpp jhale@FreeBSD.org      
security/gpgme-qt5 jhale@FreeBSD.org      
security/libassuan jhale@FreeBSD.org      
security/pinentry jhale@FreeBSD.org      
security/pinentry-curses jhale@FreeBSD.org      
security/pinentry-gnome3 jhale@FreeBSD.org      
security/pinentry-gtk2 jhale@FreeBSD.org      
security/pinentry-qt4 jhale@FreeBSD.org      
security/pinentry-qt5 jhale@FreeBSD.org      
security/pinentry-tty jhale@FreeBSD.org      
security/py-gpgme jhale@FreeBSD.org      
sysutils/duff jhale@FreeBSD.org      
sysutils/gapcmon jhale@FreeBSD.org      
sysutils/luckybackup jhale@FreeBSD.org      
sysutils/py-queuelib jhale@FreeBSD.org      
x11-clocks/plasma-applet-adjustableclock jhale@FreeBSD.org      
x11-clocks/plasma-applet-geekclock jhale@FreeBSD.org      
x11-themes/qtcurve jhale@FreeBSD.org      
x11-themes/qtcurve-gtk2 jhale@FreeBSD.org      
x11-themes/qtcurve-kde4 jhale@FreeBSD.org      
x11-themes/qtcurve-qt4 jhale@FreeBSD.org      
x11-themes/qtcurve-qt5 jhale@FreeBSD.org      
x11-themes/qtcurve-utils jhale@FreeBSD.org      
x11-toolkits/fox16 jhale@FreeBSD.org      
x11-toolkits/fox17 jhale@FreeBSD.org      
ports shown: 87   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.