|Report created on Tue Aug 22 16:45:25 2017.||back to main menu|
For explanatory information and summary details, see the notes below.
|portname||maintainer||build error logs||Problem Reports||Responsible|
|ports shown: 1||ports with build errors: 0||ports with outstanding PRs: 0|
|ports with either build errors or PRs: 0|
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 list of build errors that are detected, and a short description of each one, can be found here.
send-pr command. As such, the quality of the
entries varies greatly.
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.