Report created on Sat Mar 28 16:02:55 2015. 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
databases/ldb timur@FreeBSD.org      
databases/ntdb timur@FreeBSD.org      
databases/tdb timur@FreeBSD.org   176758: [patch] databases/tdb: samba talloc + tdb incorrect w/ non-default LOCALBASE timur@FreeBSD.org
devel/p5-Parse-Pidl timur@FreeBSD.org      
devel/talloc timur@FreeBSD.org      
devel/tevent timur@FreeBSD.org      
dns/samba-nsupdate timur@FreeBSD.org   181696: port dns/samba-nsupdate doesn't link -lgssapi_krb5, won't compile on base krb5 timur@FreeBSD.org
net/samba-libsmbclient timur@FreeBSD.org      
net/samba-nmblookup timur@FreeBSD.org      
net/samba-smbclient timur@FreeBSD.org      
net/samba36 timur@FreeBSD.org   164010: [patch] net/samba36: Split up samba scripts into more manageable pieces timur@FreeBSD.org
177786: net/samba36 net/samba-nmblookup multimedia/xbmc conflics timur@FreeBSD.org
186287: net/samba36: looping detected inside krb5_get_in_tkt on 10.0-RELEASE timur@FreeBSD.org
186694: net/samba36: samba not work in domain timur@FreeBSD.org
195659: net/samba36 fails to build with security/heimdal timur@FreeBSD.org
198246: net/samba36: build without LDAP and ADS fails, if EXP_MODULES is on timur@FreeBSD.org
198262: net/samba36: add timeout option timur@FreeBSD.org
net/samba4 timur@FreeBSD.org   183285: ports net/samba4 4.0.8 fails to build. Linking error timur@FreeBSD.org
net/samba41 timur@FreeBSD.org   186575: net/samba41: Start of Samba results in "nss_ldap: could not search LDAP server" errors timur@FreeBSD.org
191801: net/samba41 man install files not found timur@FreeBSD.org
194046: net/samba41: building Samba 4.1.x on 10.0 and 10.1-RELEASE with "DEVELOPER" option requests older/invalid gdb library timur@FreeBSD.org
197320: net/samba41: "pkg install samba41" (or samba4) pre-compiled install missing idmap_ad / ad.so shared-module! timur@FreeBSD.org
198012: net/samba41: Recent update fails on CURRENT timur@FreeBSD.org
198064: net/samba41: 4.1.17 seems to change necessary rc.conf option for winbindd timur@FreeBSD.org
ports shown: 13   ports with build errors: 0 ports with outstanding PRs: 5  
ports with either build errors or PRs: 5

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.