Report created on Fri Sep 22 15:17:00 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
accessibility/redshift feld@FreeBSD.org      
audio/mumble feld@FreeBSD.org      
audio/murmur feld@FreeBSD.org      
audio/py-musicbrainzngs feld@FreeBSD.org      
audio/py-pyacoustid feld@FreeBSD.org      
audio/py-pylast feld@FreeBSD.org      
converters/p5-Bencode feld@FreeBSD.org      
converters/py-bcode feld@FreeBSD.org      
databases/percona57-client feld@FreeBSD.org      
databases/percona57-pam-for-mysql feld@FreeBSD.org      
databases/percona57-server feld@FreeBSD.org      
devel/pcre2 feld@FreeBSD.org      
devel/pear-channel-htmlpurifier feld@FreeBSD.org      
devel/pear-htmlpurifier feld@FreeBSD.org      
devel/py-bluelet feld@FreeBSD.org      
devel/py-certsrv feld@FreeBSD.org      
devel/py-fabric3 feld@FreeBSD.org      
devel/py-inflect feld@FreeBSD.org      
devel/py-invoke feld@FreeBSD.org      
devel/py-jaraco.classes feld@FreeBSD.org      
devel/py-jaraco.functools feld@FreeBSD.org      
devel/py-jaraco.itertools feld@FreeBSD.org      
devel/py-jaraco.logging feld@FreeBSD.org      
devel/py-libtaxii feld@FreeBSD.org      
devel/py-linecache2 feld@FreeBSD.org      
devel/py-logbook feld@FreeBSD.org      
devel/py-logutils feld@FreeBSD.org      
devel/py-pyechonest feld@FreeBSD.org      
devel/py-pyhashxx feld@FreeBSD.org      
devel/py-pyral feld@FreeBSD.org      
devel/py-pystorm feld@FreeBSD.org      
devel/py-pytvmaze feld@FreeBSD.org      
devel/py-ruamel.ordereddict feld@FreeBSD.org      
devel/py-ruamel.yaml feld@FreeBSD.org      
devel/py-streamparse feld@FreeBSD.org      
devel/py-thriftpy feld@FreeBSD.org      
devel/py-traceback2 feld@FreeBSD.org      
devel/py-unittest2 feld@FreeBSD.org      
devel/py-unpaddedbase64 feld@FreeBSD.org      
devel/py-zkpython feld@FreeBSD.org      
dns/p5-Net-DRI feld@FreeBSD.org      
games/gtkevemon feld@FreeBSD.org      
irc/anope feld@FreeBSD.org      
irc/inspircd feld@FreeBSD.org      
lang/phantomjs feld@FreeBSD.org      
mail/archiveopteryx feld@FreeBSD.org ???
manpage
   
mail/archiveopteryx-devel feld@FreeBSD.org ???
manpage
   
mail/roundcube-login_info feld@FreeBSD.org      
mail/roundcube-veximaccountadmin feld@FreeBSD.org      
math/py-intspan feld@FreeBSD.org      
math/py-munkres feld@FreeBSD.org      
multimedia/ffdec feld@FreeBSD.org      
multimedia/plexmediaserver feld@FreeBSD.org      
multimedia/plexmediaserver-plexpass feld@FreeBSD.org      
multimedia/plexpy feld@FreeBSD.org      
net-im/py-matrix-synapse feld@FreeBSD.org      
net-mgmt/cdpd feld@FreeBSD.org      
net-mgmt/devmon feld@FreeBSD.org      
net-mgmt/devmon-templates feld@FreeBSD.org      
net-mgmt/nfsen feld@FreeBSD.org      
net-mgmt/py-pdagent feld@FreeBSD.org      
net-mgmt/rancid3 feld@FreeBSD.org      
net-mgmt/unifi5 feld@FreeBSD.org      
net-mgmt/xymon-client feld@FreeBSD.org      
net-mgmt/xymon-server feld@FreeBSD.org      
net-p2p/radarr feld@FreeBSD.org      
net-p2p/sonarr feld@FreeBSD.org      
net/librouteros feld@FreeBSD.org      
net/ntimed feld@FreeBSD.org      
net/py-matrix-synapse-ldap3 feld@FreeBSD.org      
net/py-pyshark feld@FreeBSD.org      
net/vnstat feld@FreeBSD.org      
security/amavis-stats feld@FreeBSD.org      
security/bearssl feld@FreeBSD.org      
security/pam-modules feld@FreeBSD.org      
security/titus feld@FreeBSD.org      
sysutils/acts feld@FreeBSD.org      
sysutils/mfid feld@FreeBSD.org      
sysutils/mptd feld@FreeBSD.org      
www/bolt feld@FreeBSD.org      
www/mod_cloudflare feld@FreeBSD.org      
www/py-pySmartDL feld@FreeBSD.org      
www/py-requests-futures feld@FreeBSD.org      
www/radicale feld@FreeBSD.org      
www/redmine-a_common_libs feld@FreeBSD.org      
www/redmine-default_assign feld@FreeBSD.org      
www/redmine-graphs feld@FreeBSD.org      
www/redmine-issue_templates feld@FreeBSD.org      
www/redmine-knowledgebase feld@FreeBSD.org      
www/redmine-ldap_sync feld@FreeBSD.org      
www/redmine-qa_contact feld@FreeBSD.org      
www/redmine-redcarpet_formatter feld@FreeBSD.org      
www/redmine-single_auth feld@FreeBSD.org      
www/redmine-wiki_notes feld@FreeBSD.org      
www/varnish-modules feld@FreeBSD.org      
www/varnish4 feld@FreeBSD.org      
www/varnish5 feld@FreeBSD.org      
ports shown: 97   ports with build errors: 2 ports with outstanding PRs: 0  
ports with either build errors or PRs: 2

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.