On Fri, Feb 21, 2014 at 12:34 PM, Agustin Martin <agmar...@debian.org>wrote:
> On Mon, Feb 17, 2014 at 12:29:49PM -0500, Dave Steele wrote:
> > 1) How does lintian know to issue this warning? Does it download
> > piuparts results?
>
> I am afraid that by manual interaction. Both work differently, lintian
> works
> on unpacked packages while pipuarts works on installed (and configured,
> along
> with the dependencies) packages.
>
I didn't know about the lintian test when I wrote earlier. I was thinking
in terms of broken symlinks left after uninstall (which is a bigger problem
IMO).
> There is a difference between an email and an implicit "suggestion" about a
> flood of bug reports.
>
Based on history, that's not what happens. There's only one bug report,
plus the purely psychic pain of knowing that there are packages out there
that could be tested, if just...
See fontconfig-config as an example. A recent failure there has ballooned
the untestable count in sid to 10% of all packages
https://piuparts.debian.org/sid/states.png
The only developer ramification - a note on the bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730361#10
I meant to focus on the psychic part. Sorry if I suggested/threatened a
flood of complaints.
Somewhere next week I plan to upload 1.22.1 to deal with this
> #625278 bug report in a way based in attached patch.
>
I appreciate that you are addressing this. Thanks.
--
"Le mieux est l'ennemi du bien" - Voltaire
