Report created on Tue Aug 22 16:58: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
audio/puddletag pawel@FreeBSD.org      
comms/efax-gtk pawel@FreeBSD.org      
deskutils/treeline pawel@FreeBSD.org      
devel/codequery pawel@FreeBSD.org      
devel/injeqt pawel@FreeBSD.org      
devel/qt-maybe pawel@FreeBSD.org      
devel/upnp pawel@FreeBSD.org      
finance/homebank pawel@FreeBSD.org      
games/gigalomania pawel@FreeBSD.org      
games/linux-dwarffortress pawel@FreeBSD.org      
games/quackle pawel@FreeBSD.org      
graphics/mirage pawel@FreeBSD.org      
mail/claws-mail pawel@FreeBSD.org      
mail/claws-mail-address_keeper pawel@FreeBSD.org      
mail/claws-mail-archiver pawel@FreeBSD.org      
mail/claws-mail-att_remover pawel@FreeBSD.org      
mail/claws-mail-attach_warner pawel@FreeBSD.org      
mail/claws-mail-bogofilter pawel@FreeBSD.org      
mail/claws-mail-bsfilter pawel@FreeBSD.org      
mail/claws-mail-clamd pawel@FreeBSD.org      
mail/claws-mail-fancy pawel@FreeBSD.org      
mail/claws-mail-fetchinfo pawel@FreeBSD.org      
mail/claws-mail-gdata pawel@FreeBSD.org      
mail/claws-mail-libravatar pawel@FreeBSD.org      
mail/claws-mail-mailmbox pawel@FreeBSD.org      
mail/claws-mail-managesieve pawel@FreeBSD.org      
mail/claws-mail-newmail pawel@FreeBSD.org      
mail/claws-mail-notification pawel@FreeBSD.org      
mail/claws-mail-pdf_viewer pawel@FreeBSD.org      
mail/claws-mail-perl pawel@FreeBSD.org      
mail/claws-mail-pgp pawel@FreeBSD.org      
mail/claws-mail-python pawel@FreeBSD.org      
mail/claws-mail-rssyl pawel@FreeBSD.org      
mail/claws-mail-spamassassin pawel@FreeBSD.org      
mail/claws-mail-spamreport pawel@FreeBSD.org      
mail/claws-mail-tnef pawel@FreeBSD.org      
mail/claws-mail-vcalendar pawel@FreeBSD.org      
mail/clawsker pawel@FreeBSD.org      
mail/libetpan pawel@FreeBSD.org      
multimedia/smplayer-skins pawel@FreeBSD.org      
multimedia/smtube pawel@FreeBSD.org      
net/libmaia pawel@FreeBSD.org      
polish/ekg pawel@FreeBSD.org      
polish/ekg2 pawel@FreeBSD.org      
polish/kadu pawel@FreeBSD.org      
polish/libgadu pawel@FreeBSD.org      
polish/qnapi pawel@FreeBSD.org linker_error    
ports-mgmt/ports-tools pawel@FreeBSD.org      
shells/wcd pawel@FreeBSD.org      
sysutils/gsmartcontrol pawel@FreeBSD.org      
sysutils/lookat pawel@FreeBSD.org      
sysutils/ncdu pawel@FreeBSD.org      
textproc/coccigrep pawel@FreeBSD.org      
textproc/meld pawel@FreeBSD.org      
x11-fonts/freefont-ttf pawel@FreeBSD.org      
x11-themes/claws-mail-themes pawel@FreeBSD.org      
x11-themes/gnome-icons-faenza pawel@FreeBSD.org      
x11-themes/lxappearance pawel@FreeBSD.org      
x11-toolkits/c++-gtk-utils pawel@FreeBSD.org      
x11/xnee pawel@FreeBSD.org      
ports shown: 60   ports with build errors: 1 ports with outstanding PRs: 0  
ports with either build errors or PRs: 1

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.