Report created on Wed Dec 2 03:24:25 2015. back to main menu

Enter a new maintainer (partial match is OK) to get information about their FreeBSD ports:


For explanatory information and summary details, see the notes below.

portname maintainer build error logs Problem Reports Responsible
databases/tdb   176758: [patch] databases/tdb: samba talloc + tdb incorrect w/ non-default LOCALBASE
202360: databases/tdb could not be built with NO_PYTHON
202397: databases/tdb: cannot build after portsnap...
dns/samba-nsupdate   181696: port dns/samba-nsupdate doesn't link -lgssapi_krb5, won't compile on base krb5
net/samba36   164010: [patch] net/samba36: Split up samba scripts into more manageable pieces
177786: net/samba36 net/samba-nmblookup multimedia/xbmc conflics
186287: net/samba36: looping detected inside krb5_get_in_tkt on 10.0-RELEASE
186694: net/samba36: samba not work in domain
198246: net/samba36: build without LDAP and ADS fails, if EXP_MODULES is on
198262: net/samba36: add timeout option
net/samba4 install_error 183285: ports net/samba4 4.0.8 fails to build. Linking error
183885: net/samba4: use net/mDNSResponder to provide Zeroconf support
net/samba41 install_error 186575: net/samba41: Start of Samba results in "nss_ldap: could not search LDAP server" errors
198064: net/samba41: 4.1.17 seems to change necessary rc.conf option for winbindd
200358: net/samba41: Compilation of 4.1.18 fails: undefined reference to ...
202315: net/samba41 ldb module version mismatch
net/samba42 install_error 202096: net/samba42: Compilation fails - Can't locate Parse/ in @INC
202565: [patch] net/samba42 Core dumping
204336: net/samba42 don't packaged w/ disabled LDAP
net/samba43   204912: net/samba43: error: unknown type name 'GSSAPI_CPP_START'
204940: /net/samba43: pkg-static: Unable to access file
ports shown: 15   ports with build errors: 3 ports with outstanding PRs: 7  
ports with either build errors or PRs: 7


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 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.