<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2014-06-06 8:50 GMT+02:00 Jaromír Mikeš <span dir="ltr"><<a href="mailto:mira.mikes@gmail.com" target="_blank">mira.mikes@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote"><a href="tel:2014-06-06%200" value="+420201406060" target="_blank">2014-06-06 0</a>:40 GMT+02:00 Jonas Smedegaard <span dir="ltr"><<a href="mailto:dr@jones.dk" target="_blank">dr@jones.dk</a>></span>:<div class="">
<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Quoting Jaromír Mikeš (2014-06-06 00:30:41)<br>
<div>> while updating documentation package I am getting unusual lintian<br>
> errors<br>
><br>
> E: tap-plugins-doc: privacy-breach-donation<br>
> usr/share/doc/tap-plugins/html/index.html<br>
> E: tap-plugins-doc: privacy-breach-logo<br>
> usr/share/doc/tap-plugins/html/index.html<br>
><br>
> Can someone have a look and advice next step?<br>
> Can these errors be overriden?<br>
<br>
</div>Enything triggered by lintian can be suppressed, if you know better: It<br>
is only automated advice, so can be wrong. But you really should know<br>
better.<br></blockquote><div><br></div></div><div>No, I don't know better ... ;)<br></div><div class=""><div><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
First step (if not done already) is to expand what lintian uses as<br>
reasoning - it can be done like this:<br>
<br>
echo "E: tap-plugins-doc: privacy-breach-donation" | lintian-inf</blockquote><div><br></div></div><div>lintian -i<br></div><div><br>E: tap-plugins-doc: privacy-breach-donation usr/share/doc/tap-plugins/html/index.html<br>
N: <br>N: This package create a potential privacy breach by fetching data from a<br>N: donation website at runtime.<br>N: <br>N: Please remove this privacy problem and add a note to the<br>N: debian/upstream/metadata file using the donation field.<br>
N: <br>N: Please replace any scripts, images, or other remote resources with<br>N: non-remote resources. It is preferable to replace them with text and<br>N: links but local copies of the remote resources are also acceptable as<br>
N: long as they don't also make calls to remote services. Please ensure<br>N: that the remote resources are suitable for Debian main before making<br>N: local copies of them.<br>N: <br>N: Refer to <a href="https://wiki.debian.org/UpstreamMetadata" target="_blank">https://wiki.debian.org/UpstreamMetadata</a> for details.<br>
N: <br>N: Severity: serious, Certainty: possible<br>N: <br>N: Check: files, Type: binary, udeb<br>N: <br>E: tap-plugins-doc: privacy-breach-logo usr/share/doc/tap-plugins/html/index.html<br>N: <br>N: This package creates a potential privacy breach by fetching a logo at<br>
N: runtime.<br>N: <br>N: Before using a local copy you should check that the logo is suitable for<br>N: main. Ask debian-legal for advice.<br>N: <br>N: Please replace any scripts, images, or other remote resources with<br>
N: non-remote resources. It is preferable to replace them with text and<br>N: links but local copies of the remote resources are also acceptable as<br>N: long as they don't also make calls to remote services. Please ensure<br>
N: that the remote resources are suitable for Debian main before making<br>N: local copies of them.<br>N: <br>N: Severity: serious, Certainty: possible<br>N: <br>N: Check: files, Type: binary, udeb </div>
</div></div></div></blockquote><div><br><br></div><div>I am just thinking just provide link to on-line documentation in "description" of tap-plugins <br>and remove tap-plugins-doc package.<br><br></div><div>Is on-line doc enough?<br>
</div><div><br></div><div>Opinions?<br><br></div><div>best regards<br><br></div><div>mira<br></div></div><br></div></div>