Report created on Fri Mar 24 10:28:20 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/squeeze xfce@FreeBSD.org      
archivers/thunar-archive-plugin xfce@FreeBSD.org      
audio/thunar-media-tags-plugin xfce@FreeBSD.org      
audio/xfce4-mixer xfce@FreeBSD.org      
audio/xfce4-mpc-plugin xfce@FreeBSD.org      
audio/xfce4-pulseaudio-plugin xfce@FreeBSD.org      
audio/xfmpc xfce@FreeBSD.org      
deskutils/orage xfce@FreeBSD.org      
deskutils/xfce4-notes-plugin xfce@FreeBSD.org      
deskutils/xfce4-tumbler xfce@FreeBSD.org      
deskutils/xfce4-volumed-pulse xfce@FreeBSD.org      
deskutils/xfce4-xkb-plugin xfce@FreeBSD.org      
devel/xfce4-dev-tools xfce@FreeBSD.org      
devel/xfce4-vala xfce@FreeBSD.org      
editors/mousepad xfce@FreeBSD.org      
graphics/ristretto xfce@FreeBSD.org      
mail/xfce4-mailwatch-plugin xfce@FreeBSD.org      
math/xfce4-calculator-plugin xfce@FreeBSD.org      
misc/xfce4-appfinder xfce@FreeBSD.org      
misc/xfce4-weather-plugin xfce@FreeBSD.org      
misc/xfce4-wm-themes xfce@FreeBSD.org      
multimedia/xfce4-parole xfce@FreeBSD.org      
print/xfce4-print xfce@FreeBSD.org      
science/xfce4-equake-plugin xfce@FreeBSD.org      
sysutils/garcon xfce@FreeBSD.org      
sysutils/xfburn xfce@FreeBSD.org      
sysutils/xfce4-battery-plugin xfce@FreeBSD.org      
sysutils/xfce4-cpugraph-plugin xfce@FreeBSD.org      
sysutils/xfce4-fsguard-plugin xfce@FreeBSD.org      
sysutils/xfce4-genmon-plugin xfce@FreeBSD.org      
sysutils/xfce4-mount-plugin xfce@FreeBSD.org      
sysutils/xfce4-netload-plugin xfce@FreeBSD.org      
sysutils/xfce4-power-manager xfce@FreeBSD.org      
sysutils/xfce4-settings xfce@FreeBSD.org      
sysutils/xfce4-systemload-plugin xfce@FreeBSD.org      
sysutils/xfce4-wavelan-plugin xfce@FreeBSD.org      
textproc/xfce4-dict-plugin xfce@FreeBSD.org      
www/midori xfce@FreeBSD.org      
www/xfce4-smartbookmark-plugin xfce@FreeBSD.org      
x11-clocks/xfce4-datetime-plugin xfce@FreeBSD.org      
x11-clocks/xfce4-timer-out-plugin xfce@FreeBSD.org      
x11-clocks/xfce4-timer-plugin xfce@FreeBSD.org      
x11-fm/thunar xfce@FreeBSD.org      
x11-fm/thunar-vfs xfce@FreeBSD.org      
x11-themes/gtk-xfce-engine xfce@FreeBSD.org      
x11-toolkits/libxfce4gui xfce@FreeBSD.org      
x11-wm/xfce4 xfce@FreeBSD.org      
x11-wm/xfce4-desktop xfce@FreeBSD.org      
x11-wm/xfce4-panel xfce@FreeBSD.org      
x11-wm/xfce4-session xfce@FreeBSD.org      
x11-wm/xfce4-wm xfce@FreeBSD.org      
x11/libexo xfce@FreeBSD.org      
x11/libxfce4menu xfce@FreeBSD.org      
x11/libxfce4util xfce@FreeBSD.org      
x11/xfce4-clipman-plugin xfce@FreeBSD.org      
x11/xfce4-conf xfce@FreeBSD.org      
x11/xfce4-dashboard xfce@FreeBSD.org      
x11/xfce4-embed-plugin xfce@FreeBSD.org      
x11/xfce4-goodies xfce@FreeBSD.org      
x11/xfce4-quicklauncher-plugin xfce@FreeBSD.org      
x11/xfce4-screenshooter-plugin xfce@FreeBSD.org      
x11/xfce4-taskmanager xfce@FreeBSD.org      
x11/xfce4-terminal xfce@FreeBSD.org      
x11/xfce4-verve-plugin xfce@FreeBSD.org      
x11/xfce4-whiskermenu-plugin xfce@FreeBSD.org      
x11/xfce4-wmdock-plugin xfce@FreeBSD.org      
ports shown: 66   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.