Bug#919162: lintian.d.o apears to report many failures twice
Chris Lamb:
> Ian Campbell wrote:
>
>>> aapt 1:8.1.0+r23-3 (binary) ($maintainer)
>>>
>>> * usr/lib/android-sdk/build-tools/debian/aapt [amd64, i386]
>>> * usr/lib/android-sdk/build-tools/debian/aapt2
>>
>> That's what I was thinking for the ideal case too.
>
> (This is probably the same effort as the separate "[amd64]" and
> "[i386]" lines; its the duplicate detection and updating the data
> structures that will be problematic, if anything.)
>
> Niels, any tips/pointers on how I get a very very simple reporting
> framework running locally? Perhaps even just one package? I've been
> previously just making my changes here blind...
>
>
> Regards,
>
In this case, you only need the report-generator to work. This
simplifies some things as it can be called directly if you do some setup
manually.
* Create a config.yml with the relevant bits (copy and adapt the one
from lindsay if needed). I believe you only need to consider:
storage.state-cache (writable directory)
storage.reports-work-dir (creatable non-existent directory)
storage.historical-data-dir (optional; only needed for graphs)
template-variables.* (for variables used in the templates)
* (optionally) create an harness state cache file (copy and adapt the
one from lindsay if in doubt). As I recall, it is redundant in this
case and its absence will just mean the results is tied to the
report for the maintainer "unknown".
That was the setup. Then the testing works like this:
* Generate a lintian log file that should be parsed/generate the
report[1].
* Delete/rename the directory denoted by storage.reports-work-dir if it
exists (e.g. from a previous test)
* Run the reporting html command with:
frontend/dplint reporting-html-reports \
--reporting-config <your-config.yml>
<lintian.log>
The above is from memory and may need some tweaking to work in practise.
Thanks,
~Niels
[1] Minimum being:
lintian \
--verbose \
--exp-output=format=fullewi \
<whatever you want here>
Reply to: