Report created on Wed Jun 28 09:04:12 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/py-python-snappy antoine@FreeBSD.org      
converters/py-bencode antoine@FreeBSD.org      
deskutils/dosage antoine@FreeBSD.org      
devel/libbde antoine@FreeBSD.org      
devel/libesedb antoine@FreeBSD.org      
devel/libevt antoine@FreeBSD.org      
devel/libevtx antoine@FreeBSD.org      
devel/libfsntfs antoine@FreeBSD.org      
devel/libfwnt antoine@FreeBSD.org      
devel/libfwsi antoine@FreeBSD.org      
devel/liblnk antoine@FreeBSD.org      
devel/libmsiecf antoine@FreeBSD.org      
devel/libolecf antoine@FreeBSD.org      
devel/libpff antoine@FreeBSD.org      
devel/libqcow antoine@FreeBSD.org      
devel/libregf antoine@FreeBSD.org      
devel/libscca antoine@FreeBSD.org      
devel/libsigscan antoine@FreeBSD.org      
devel/libsmdev antoine@FreeBSD.org      
devel/libsmraw antoine@FreeBSD.org      
devel/libvhdi antoine@FreeBSD.org      
devel/libvmdk antoine@FreeBSD.org      
devel/libvslvm antoine@FreeBSD.org      
devel/py-binplist antoine@FreeBSD.org      
devel/py-codegen antoine@FreeBSD.org      
devel/py-construct antoine@FreeBSD.org      
devel/py-docopt antoine@FreeBSD.org      
devel/py-efilter antoine@FreeBSD.org      
devel/py-intervaltree antoine@FreeBSD.org      
devel/py-jdcal antoine@FreeBSD.org      
devel/py-olefile antoine@FreeBSD.org      
devel/py-ordered-set antoine@FreeBSD.org      
devel/py-pefile antoine@FreeBSD.org      
devel/py-pyelftools antoine@FreeBSD.org      
devel/py-sortedcontainers antoine@FreeBSD.org      
devel/py-weakrefmethod antoine@FreeBSD.org      
devel/py3-docopt antoine@FreeBSD.org      
devel/rubygem-metasm antoine@FreeBSD.org      
devel/rubygem-windows_error antoine@FreeBSD.org      
emulators/py-unicorn antoine@FreeBSD.org      
emulators/unicorn antoine@FreeBSD.org missing_header    
net/rubygem-network_interface antoine@FreeBSD.org      
net/rubygem-packetfu antoine@FreeBSD.org      
net/rubygem-pcaprub antoine@FreeBSD.org      
net/rubygem-ruby_smb antoine@FreeBSD.org      
net/tcpflow antoine@FreeBSD.org      
security/py-artifacts antoine@FreeBSD.org      
security/py-cybox antoine@FreeBSD.org      
security/py-dfdatetime antoine@FreeBSD.org      
security/py-dfvfs antoine@FreeBSD.org      
security/py-dfwinreg antoine@FreeBSD.org      
security/py-maec antoine@FreeBSD.org      
security/py-mixbox antoine@FreeBSD.org      
security/py-plaso antoine@FreeBSD.org      
security/py-pyaff4 antoine@FreeBSD.org      
security/py-pydeep antoine@FreeBSD.org      
security/py-python-registry antoine@FreeBSD.org      
security/py-rekall antoine@FreeBSD.org      
security/py-rekall-core antoine@FreeBSD.org      
security/py-rekall_gui [I] antoine@FreeBSD.org      
security/py-stix antoine@FreeBSD.org      
security/py-volatility antoine@FreeBSD.org      
security/py-yara antoine@FreeBSD.org      
security/regripper antoine@FreeBSD.org      
security/rifiuti2 antoine@FreeBSD.org      
security/rubygem-metasploit-concern antoine@FreeBSD.org      
security/rubygem-metasploit-credential antoine@FreeBSD.org      
security/rubygem-metasploit-model antoine@FreeBSD.org      
security/rubygem-metasploit-payloads antoine@FreeBSD.org      
security/rubygem-metasploit_data_models antoine@FreeBSD.org      
security/rubygem-metasploit_payloads-mettle antoine@FreeBSD.org      
security/rubygem-nessus_rest antoine@FreeBSD.org      
security/rubygem-nexpose antoine@FreeBSD.org      
security/rubygem-openvas-omp antoine@FreeBSD.org      
security/rubygem-origami antoine@FreeBSD.org      
security/rubygem-recog antoine@FreeBSD.org      
security/rubygem-rex-arch antoine@FreeBSD.org      
security/rubygem-rex-bin_tools antoine@FreeBSD.org      
security/rubygem-rex-core antoine@FreeBSD.org      
security/rubygem-rex-encoder antoine@FreeBSD.org      
security/rubygem-rex-exploitation antoine@FreeBSD.org      
security/rubygem-rex-java antoine@FreeBSD.org      
security/rubygem-rex-mime antoine@FreeBSD.org      
security/rubygem-rex-nop antoine@FreeBSD.org      
security/rubygem-rex-ole antoine@FreeBSD.org      
security/rubygem-rex-powershell antoine@FreeBSD.org      
security/rubygem-rex-random_identifier antoine@FreeBSD.org      
security/rubygem-rex-registry antoine@FreeBSD.org      
security/rubygem-rex-rop_builder antoine@FreeBSD.org      
security/rubygem-rex-socket antoine@FreeBSD.org      
security/rubygem-rex-sslscan antoine@FreeBSD.org      
security/rubygem-rex-struct2 antoine@FreeBSD.org      
security/rubygem-rex-text antoine@FreeBSD.org      
security/rubygem-rex-zip antoine@FreeBSD.org      
security/wapiti antoine@FreeBSD.org      
security/yara antoine@FreeBSD.org      
sysutils/afflib antoine@FreeBSD.org      
sysutils/libfvde antoine@FreeBSD.org      
sysutils/py-analyzemft antoine@FreeBSD.org      
sysutils/py-pytsk antoine@FreeBSD.org      
sysutils/sleuthkit antoine@FreeBSD.org      
textproc/kibana3 antoine@FreeBSD.org      
textproc/py-acora antoine@FreeBSD.org      
textproc/py-et_xmlfile antoine@FreeBSD.org      
textproc/py-openpyxl antoine@FreeBSD.org      
textproc/py-pyelasticsearch antoine@FreeBSD.org      
textproc/py-xlsxwriter antoine@FreeBSD.org      
textproc/py-yapf antoine@FreeBSD.org      
www/faup antoine@FreeBSD.org      
www/py-flask-sockets antoine@FreeBSD.org      
www/py-gevent-websocket antoine@FreeBSD.org      
ports shown: 111   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.