Report created on Thu Apr 27 05:11:29 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
benchmarks/fio bapt@FreeBSD.org linker_error    
devel/aarch64-binutils bapt@FreeBSD.org configure_error    
devel/aarch64-gcc bapt@FreeBSD.org      
devel/aarch64-none-elf-binutils bapt@FreeBSD.org      
devel/aarch64-none-elf-gcc bapt@FreeBSD.org configure_error    
devel/aarch64-xtoolchain-gcc bapt@FreeBSD.org      
devel/amd64-binutils bapt@FreeBSD.org      
devel/amd64-gcc bapt@FreeBSD.org ???
perl
   
devel/amd64-xtoolchain-gcc bapt@FreeBSD.org      
devel/arm-gnueabi-binutils bapt@FreeBSD.org      
devel/arm-none-eabi-binutils bapt@FreeBSD.org      
devel/arm-none-eabi-gcc bapt@FreeBSD.org configure_error    
devel/binutils bapt@FreeBSD.org      
devel/libedit bapt@FreeBSD.org      
devel/libmill bapt@FreeBSD.org      
devel/mips-binutils bapt@FreeBSD.org      
devel/mips-gcc bapt@FreeBSD.org      
devel/mips-xtoolchain-gcc bapt@FreeBSD.org      
devel/mips64-binutils bapt@FreeBSD.org      
devel/mips64-gcc bapt@FreeBSD.org process_failed    
devel/mips64-xtoolchain-gcc bapt@FreeBSD.org      
devel/openmp bapt@FreeBSD.org ???    
devel/p5-AnyEvent-I3 bapt@FreeBSD.org      
devel/pkgconf bapt@FreeBSD.org      
devel/powerpc64-binutils bapt@FreeBSD.org      
devel/powerpc64-gcc bapt@FreeBSD.org      
devel/powerpc64-xtoolchain-gcc bapt@FreeBSD.org      
devel/py-cliapp bapt@FreeBSD.org      
devel/py-cmdtest bapt@FreeBSD.org      
devel/py-ttystatus bapt@FreeBSD.org      
devel/riscv64-xtoolchain-gcc bapt@FreeBSD.org      
devel/slibtool bapt@FreeBSD.org      
devel/sparc64-binutils bapt@FreeBSD.org      
devel/sparc64-gcc bapt@FreeBSD.org      
devel/sparc64-xtoolchain-gcc bapt@FreeBSD.org      
graphics/pdfpc bapt@FreeBSD.org      
mail/abook bapt@FreeBSD.org      
mail/neomutt bapt@FreeBSD.org      
math/libxls bapt@FreeBSD.org      
math/libxlsxwriter bapt@FreeBSD.org      
math/sc-im bapt@FreeBSD.org      
print/indexinfo bapt@FreeBSD.org      
security/kickpass bapt@FreeBSD.org      
security/py-yubioath-desktop bapt@FreeBSD.org      
shells/zsh bapt@FreeBSD.org      
textproc/diffstat bapt@FreeBSD.org      
textproc/docbook2mdoc bapt@FreeBSD.org      
textproc/lowdown bapt@FreeBSD.org      
textproc/minixmlto bapt@FreeBSD.org      
textproc/pod2mdoc bapt@FreeBSD.org      
textproc/texi2mdoc bapt@FreeBSD.org      
www/cblog bapt@FreeBSD.org      
www/cplanet bapt@FreeBSD.org      
www/kcgi bapt@FreeBSD.org      
x11-wm/i3 bapt@FreeBSD.org      
x11/i3lock bapt@FreeBSD.org      
x11/i3status bapt@FreeBSD.org      
x11/xcbautolock bapt@FreeBSD.org      
ports shown: 58   ports with build errors: 7 ports with outstanding PRs: 0  
ports with either build errors or PRs: 7

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.