Report created on Thu May 25 18:26:57 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
cad/sweethome3d matthias@petermann-it.de      
databases/py-peewee matthias@petermann-it.de      
finance/tryton28 matthias@petermann-it.de      
finance/trytond28 matthias@petermann-it.de      
finance/trytond28_account matthias@petermann-it.de      
finance/trytond28_account_asset matthias@petermann-it.de      
finance/trytond28_account_be matthias@petermann-it.de      
finance/trytond28_account_invoice matthias@petermann-it.de      
finance/trytond28_account_invoice_history matthias@petermann-it.de      
finance/trytond28_account_invoice_line_standalone matthias@petermann-it.de      
finance/trytond28_account_product matthias@petermann-it.de      
finance/trytond28_account_statement matthias@petermann-it.de      
finance/trytond28_account_stock_anglo_saxon matthias@petermann-it.de      
finance/trytond28_account_stock_continental matthias@petermann-it.de      
finance/trytond28_analytic_account matthias@petermann-it.de      
finance/trytond28_analytic_invoice matthias@petermann-it.de      
finance/trytond28_analytic_purchase matthias@petermann-it.de      
finance/trytond28_analytic_sale matthias@petermann-it.de      
finance/trytond28_calendar matthias@petermann-it.de      
finance/trytond28_calendar_classification matthias@petermann-it.de      
finance/trytond28_calendar_scheduling matthias@petermann-it.de      
finance/trytond28_calendar_todo matthias@petermann-it.de      
finance/trytond28_carrier matthias@petermann-it.de      
finance/trytond28_carrier_percentage matthias@petermann-it.de      
finance/trytond28_carrier_weight matthias@petermann-it.de      
finance/trytond28_company matthias@petermann-it.de      
finance/trytond28_company_work_time matthias@petermann-it.de      
finance/trytond28_country matthias@petermann-it.de      
finance/trytond28_currency matthias@petermann-it.de      
finance/trytond28_dashboard matthias@petermann-it.de      
finance/trytond28_ldap_authentication matthias@petermann-it.de      
finance/trytond28_party matthias@petermann-it.de      
finance/trytond28_party_siret matthias@petermann-it.de      
finance/trytond28_party_vcarddav matthias@petermann-it.de      
finance/trytond28_product matthias@petermann-it.de      
finance/trytond28_product_attribute matthias@petermann-it.de      
finance/trytond28_product_cost_fifo matthias@petermann-it.de      
finance/trytond28_product_cost_history matthias@petermann-it.de      
finance/trytond28_product_measurements matthias@petermann-it.de      
finance/trytond28_product_price_list matthias@petermann-it.de      
finance/trytond28_production matthias@petermann-it.de      
finance/trytond28_project matthias@petermann-it.de      
finance/trytond28_project_invoice matthias@petermann-it.de      
finance/trytond28_project_plan matthias@petermann-it.de      
finance/trytond28_project_revenue matthias@petermann-it.de      
finance/trytond28_purchase matthias@petermann-it.de      
finance/trytond28_purchase_invoice_line_standalone matthias@petermann-it.de      
finance/trytond28_purchase_shipment_cost matthias@petermann-it.de      
finance/trytond28_sale matthias@petermann-it.de      
finance/trytond28_sale_opportunity matthias@petermann-it.de      
finance/trytond28_sale_price_list matthias@petermann-it.de      
finance/trytond28_sale_shipment_cost matthias@petermann-it.de      
finance/trytond28_sale_supply matthias@petermann-it.de      
finance/trytond28_sale_supply_drop_shipment matthias@petermann-it.de      
finance/trytond28_stock matthias@petermann-it.de      
finance/trytond28_stock_forecast matthias@petermann-it.de      
finance/trytond28_stock_inventory_location matthias@petermann-it.de      
finance/trytond28_stock_location_sequence matthias@petermann-it.de      
finance/trytond28_stock_lot matthias@petermann-it.de      
finance/trytond28_stock_product_location matthias@petermann-it.de      
finance/trytond28_stock_split matthias@petermann-it.de      
finance/trytond28_stock_supply matthias@petermann-it.de      
finance/trytond28_stock_supply_day matthias@petermann-it.de      
finance/trytond28_stock_supply_forecast matthias@petermann-it.de      
finance/trytond28_stock_supply_production matthias@petermann-it.de      
finance/trytond28_timesheet matthias@petermann-it.de      
french/trytond28_account_fr matthias@petermann-it.de      
german/trytond28_account_de_skr03 matthias@petermann-it.de      
www/trytond28_google_maps matthias@petermann-it.de      
x11-themes/xfce-icons-elementary matthias@petermann-it.de      
ports shown: 70   ports with build errors: 0 ports with outstanding PRs: 0  
ports with either build errors or PRs: 0

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.