Report created on Sat Apr 29 07:56:16 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/py-pyliblzma dbn@FreeBSD.org      
audio/flake dbn@FreeBSD.org      
audio/kaudiocreator dbn@FreeBSD.org      
audio/soundkonverter dbn@FreeBSD.org      
deskutils/plasma-applet-cwp dbn@FreeBSD.org      
devel/eric6 dbn@FreeBSD.org      
devel/kdesvn-kde4 dbn@FreeBSD.org      
devel/py-typed-ast dbn@FreeBSD.org      
devel/svn2git dbn@FreeBSD.org      
emulators/i386-wine [I] dbn@FreeBSD.org      
emulators/i386-wine-devel [I] dbn@FreeBSD.org      
emulators/i386-wine-staging [I] dbn@FreeBSD.org      
emulators/wine-mono dbn@FreeBSD.org      
emulators/wine-mono-devel dbn@FreeBSD.org      
finance/R-cran-fBasics dbn@FreeBSD.org      
finance/R-cran-fGarch dbn@FreeBSD.org      
finance/R-cran-timeDate dbn@FreeBSD.org      
finance/R-cran-timeSeries dbn@FreeBSD.org      
finance/R-cran-tseries dbn@FreeBSD.org      
graphics/s2tc dbn@FreeBSD.org      
math/R-cran-RSvgDevice dbn@FreeBSD.org      
math/R-cran-car dbn@FreeBSD.org      
math/R-cran-gss dbn@FreeBSD.org      
math/R-cran-quadprog dbn@FreeBSD.org      
math/R-cran-stabledist dbn@FreeBSD.org      
multimedia/py-ffmpeg dbn@FreeBSD.org      
science/vmd [I] dbn@FreeBSD.org      
sysutils/py-plumbum dbn@FreeBSD.org      
x11-themes/cursor-crystal-theme dbn@FreeBSD.org      
x11-themes/kde4-style-oxygen-transparent dbn@FreeBSD.org      
x11-toolkits/py-kivy dbn@FreeBSD.org      
ports shown: 31   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.